Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:68648
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain zend.com from 209.85.214.181 cause and error)
MIME-Version: 1.0
In-Reply-To: <521E534E.2060603@sugarcrm.com>
References: <CALjhHG8FPmGYSk5g6JV7_Hq7GAeFH+US6R3K9FO_1Thneju+LA@mail.gmail.com>
	<521E468E.5070406@sugarcrm.com>
	<CAPJnDK2a_x==kG-74jQjmQDfiS_foo2yPgsUyrcN7VsOmm6GBQ@mail.gmail.com>
	<521E534E.2060603@sugarcrm.com>
Date: Wed, 28 Aug 2013 23:13:17 +0300
Message-ID: <CAPJnDK1dNhjcaecyN9t=5juRcaU3JKf+NSYuK=Wer=za-tOB6g@mail.gmail.com>
To: Stas Malyshev <smalyshev@sugarcrm.com>
Cc: =?UTF-8?B?T25kxZllaiBTdXLDvQ==?= <ondrej@sury.org>, 
	PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=089e013d0c22bef04504e5079e71
Subject: Re: [PHP-DEV] Attitude against distributions... (Was: JSON non-free license)
From: lior.k@zend.com (Lior Kaplan)

--089e013d0c22bef04504e5079e71
Content-Type: text/plain; charset=UTF-8

On Wed, Aug 28, 2013 at 10:45 PM, Stas Malyshev <smalyshev@sugarcrm.com>wrote:

> Hi!
>
> > http://marc.info/?l=php-internals&m=136768085009866&w=2
>
> This is great but this is not exactly what I'm talking about. There's a
> big difference between having an extension that does JSON in PECL and
> replacing part of PHP core (and very commonly used part) by something
> else.
>

Well, having the new implementation in PECL is a logical step to publish
the code and let people test it.

His mail offers (my emphasis):

1/ update existing pecl/json extension
> - on pecl for older PHP 5.3 - 5.5
> * - on php-src in master / 5.6 *


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.

I agree to what you said about a bug not being a discussion. But it was the
first try to communicate with the community. Today, I would raise the issue
differently, but Remi's mail with the subject of "Proposal: new
implementation of JSON extension" should have been a good start.

Kaplan

--089e013d0c22bef04504e5079e71--