Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:68654 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 35576 invoked from network); 28 Aug 2013 21:40:10 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 28 Aug 2013 21:40:10 -0000 Authentication-Results: pb1.pair.com header.from=smalyshev@sugarcrm.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=smalyshev@sugarcrm.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain sugarcrm.com designates 108.166.43.75 as permitted sender) X-PHP-List-Original-Sender: smalyshev@sugarcrm.com X-Host-Fingerprint: 108.166.43.75 smtp75.ord1c.emailsrvr.com Linux 2.6 Received: from [108.166.43.75] ([108.166.43.75:35384] helo=smtp75.ord1c.emailsrvr.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 43/A7-33204-A3E6E125 for ; Wed, 28 Aug 2013 17:40:10 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp2.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id CC9301E80FE; Wed, 28 Aug 2013 17:40:07 -0400 (EDT) X-Virus-Scanned: OK Received: by smtp2.relay.ord1c.emailsrvr.com (Authenticated sender: smalyshev-AT-sugarcrm.com) with ESMTPSA id 6B4201E80B2; Wed, 28 Aug 2013 17:40:07 -0400 (EDT) Message-ID: <521E6E36.4060007@sugarcrm.com> Date: Wed, 28 Aug 2013 14:40:06 -0700 Organization: SugarCRM User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 MIME-Version: 1.0 To: Lior Kaplan CC: =?UTF-8?B?T25kxZllaiBTdXLDvQ==?= , PHP Internals References: <521E468E.5070406@sugarcrm.com> <521E534E.2060603@sugarcrm.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Attitude against distributions... (Was: JSON non-free license) From: smalyshev@sugarcrm.com (Stas Malyshev) Hi! > And while the issue was first reported by Debian, the other > distributions share the same concerns. This is why PHP should consider > this - because the other parts of the eco-system are already going > forward with this. What we need to consider this extension as a replacement for core JSON is: - explanation of advantages and disadvantages (noting that for most PHP users "weird license" is not a significant disadvantage of the extension) of the change - RFC - API description - potential BC problems - performance impact -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227