Probably the language which most commonly handles JSON is JavaScript itself. So a major chunk
of the benefit, possibly even the majority of the benefit, would be immediate: eval(),
application config files expressed in JSON, etc.
And as you alluded to (also I CAN HAZ CUSTIM CLAZZES?) JSON will probably
eventually have versions.
On 3/11/2011 12:55 PM, Dean Landolt wrote:
On Fri, Mar 11, 2011 at 3:48 PM, Charles Kendrick <[email protected]
<mailto:[email protected]>> wrote:
Not so - order-preserving implementations are backwards compatible with
non-order-preserving implementations. Just rev the spec, and like any
other versioned
spec, developers can use the new behavior when they know the application
environment uses
only the new version.
The JSON spec has no version number, intentionally -- it would have to be
supersetted entirely.
You could make the argument that perhaps it's about time (I CAN HAZ DATES?) but
that's a much
bigger challenge, and your claimed advantages to JSON handling would still be
moot until
ECMAScript adopted your JSON replacement.
_______________________________________________
es-discuss mailing list
[email protected]
https://mail.mozilla.org/listinfo/es-discuss
