The Debian page on this issue links to a cleanroom implementation of the same api, from Android: https://android.googlesource.com/platform/libcore/+log/master/json
Could this be used in the web console to avoid breaking changes? Neil On 28 Oct 2016 12:46 p.m., "Carsten Ziegeler" <[email protected]> wrote: > Felix Meschberger wrote > > Hi all > > > > Over at legal-discuss there is a discussion of whether the json.org > library with the amended MIT license (remember the „use for good not evil“ > clause ?) should be „banned“ by reconsidering the „A“ rating of this > license (assuming the clause is just a joke) and turning it into an „X“ > rating (don’t use based on Debian’s and other’s considerations: > > > > https://wiki.debian.org/qa.debian.org/jsonevil > > https://www.cnet.com/news/dont-be-evil-google-spurns-no-evil-software/ > > > > It is not decided yet. But for the web console we should probably be > prepared. > > > > Plenty of alternatives exist: Jackson, GSon, and IMHO quite interesting > javax.json (https://json-processing-spec.java.net/) with a RI from > glassfish (https://jsonp.java.net/). > > > > Assuming we would have to change things, I propose we reimplement the > API of the json.org library with javax.json using the Glassfish RI. > > > > WDYT ? > > > I think the biggest challenge is the web console - where we have usage > of json.org in the API, so we can't replace that without breaking the API. > Those methods are deprecated for quiet some time, but removing them > would require to bump the major version. > > Carsten > > > > -- > Carsten Ziegeler > Adobe Research Switzerland > [email protected] > >
