News for hackers. Stuff that matters.
Re:JSON5 is a proposed extension to JSON by nitrogen on Sunday March 02, 2014 @02:26AM (#7328122)
It makes perfect sense -- if you provide a freeform content section of an otherwise strictly formed document (for interoperability reasons), then people will abuse it to store arbitrary, uninteroperable data (as was seen with binary blobs being dumped into XML).

The point of a standardized serialization format is well-defined parsing semantics and universal interoperability.

Re:JSON5 is a proposed extension to JSON by coldtea on Sunday March 02, 2014 @08:01AM (#7328990)
>It makes perfect sense -- if you provide a freeform content section of an otherwise strictly formed document (for interoperability reasons), then people will abuse it to store arbitrary, uninteroperable data (as was seen with binary blobs being dumped into XML).

That will then be their own bloody problem, not Crockfords.

Re:JSON5 is a proposed extension to JSON by makomk on Sunday March 02, 2014 @07:36AM (#7328929)
Except that in practice, this has just meant that people have defined their own ad-hoc extensions to JSON that add support for comments, since it's so useful for stuff like JSON-formatted config files.
Re:JSON5 is a proposed extension to JSON by TazeTSchnitzel on Sunday March 02, 2014 @11:20AM (#7329589)
It's also meant that JSON documents don't have data encoded in comments. Working as intended.
Re:JSON5 is a proposed extension to JSON by einhverfr on Sunday March 02, 2014 @05:08AM (#7328560)
Indeed. I see SQL comments and Postgres COMMENT ON statements used to send information to applications. Really funny, that....
Re:JSON5 is a proposed extension to JSON by troels on Sunday March 02, 2014 @04:50AM (#7328498)
And you can't base64 encode it and store it in a string?
Re:JSON5 is a proposed extension to JSON by rat87 on Sunday March 02, 2014 @04:22AM (#7328422)
I thought xml was developed to be able to include binary parts on purpose since it can be useful.