Bug #63520 [Com]: JSON extension includes a problematic license statement

From: Date: Wed, 29 Jan 2014 23:59:52 +0000
Subject: Bug #63520 [Com]: JSON extension includes a problematic license statement
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-184079@lists.php.net to get a copy of this message 
Edit report at https://bugs.php.net/bug.php?id=63520&edit=1

 ID:                 63520
 Comment by:         tim at vanillaforums dot com
 Reported by:        kaplan at debian dot org
 Summary:            JSON extension includes a problematic license
                     statement
 Status:             Assigned
 Type:               Bug
 Package:            JSON related
 PHP Version:        Irrelevant
 Assigned To:        remi
 Block user comment: N
 Private report:     N

 New Comment:

I think I speak for most PHP end users when I say I *literally* couldn't care less what
underlying JSON implementation is used in the end, as long as the json_* functions remain core,
default-enabled functions.

The utter childishness of some of the comments in this thread gives me a non-trivial level of
concern, but I'm hoping we don't enter a future where json_* cannot be relied on to exist.

Yesterday a co-worker upgraded to PHP 5.5 and found that he was missing these vital functions. The
revelation that THIS of all things was the cause left us speechless.


Previous Comments:
------------------------------------------------------------------------
[2013-12-27 21:10:52] scott at arciszewski dot me

I definitely would like to encourage the adoption of https://github.com/remicollet/pecl-json-c in
all distributions of PHP if for no other reason than the JSON_PARSER_NOTSTRICT option:
* comments are allowed in json string/files (Using /* */ or // until end of line)

This would allow the use of commented JSON configuration files, which is awesome.

------------------------------------------------------------------------
[2013-08-30 18:12:46] jsjohnst@php.net

When the decision is made, can we get a public statement on the site about it? 
Posts like the one on iteration99 (dot) com are only raising the confusion level 
among devs when really this isn't something directly impacting most PHP 
developers.

------------------------------------------------------------------------
[2013-08-29 01:04:59] v3qqd2w4 dot ov0 at 20minutemail dot com

I hate to add to the noise, but has anyone pointed out to JSON that leaving it to a court to
interpret "shall be used for Good, not Evil" is a highly unpredictable outcome? The entire
license could be invalidated -- since it has no severability clause -- meaning nobody except the
copyright owner is allowed to use any of the JSON code for anything. Is that really a potential
outcome that they want?

------------------------------------------------------------------------
[2013-08-28 10:26:30] dsp@php.net

I'd be more than happy to see a json extension drop-in. Obviously we cannot 
change the license without the authors permissions, so a drop-in would be the 
best approach.

------------------------------------------------------------------------
[2013-08-28 09:20:59] pajoye@php.net

Besides the license issue, which is a problem but not a php one, Remi's new 
extension brings its lot of nice new stuff.

Please leave this open and add a link to the new extension and RFC, to avoid 
endless confusion here.

------------------------------------------------------------------------


The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at

    https://bugs.php.net/bug.php?id=63520


-- 
Edit this bug report at https://bugs.php.net/bug.php?id=63520&edit=1

Thread (40 messages)

« previous php.bugs (#184079) next »