Proposed to Drop: JEP 198: Light-Weight JSON API

[Alan Williamson]

Mark, i would love to understand your reasoning behind this move.

Java has always suffered from poor core support for popular formats.   
It took a long time before XML came to the core language and while that 
happened there was no real great alternative.

JSON is a little different I grant you, considering how strong and 
popular Jackson/GSON/Mongo 3rd party libraries are.

However I believe JSON will be with the industry far longer than even 
XML.   With its deep roots in JavaScript (which Java has entered that 
game in a big way with Nashorn), JSON is the number one choice for web 
services, data storage and generate NoSQL communications.

By not having an official answer for this format, is going to hurt Java 
in the long run.

thanks

a

-- 
   http://alan.aw20.net/



On 04/12/2014 14:43, mark.reinhold at oracle.com wrote:
> This JEP [1] would be a useful addition to the platform but, in the grand
> scheme of things, it's not as important as the other features that Oracle
> is funding, or considering funding, for JDK 9.  I've therefore moved it
> to the Proposed to Drop state.
>
> We may reconsider this JEP for JDK 10 or a later release, especially if
> new language features such as value types [2] and generics over primitive
> types (JEP 218 [3]) enable a more compact and expressive API.
>
> - Mark
>
>
> [1] http://openjdk.java.net/jeps/198
> [2] http://cr.openjdk.java.net/~jrose/values/values-0.html
> [3] http://openjdk.java.net/jeps/218