JSON5

I think that it's really a shame to see people slamming aseemk here. He had an idea, worked on it, and released it. That's fantastic. There are a few constructive comments here…

You know that something has gone very deeply wrong somewhere when people oppose your project because they are ideologically opposed to comments. In my own experience, finding out…

Please, don't call it JSON. There is only one JSON, and you didn't make it. It's cool that you made this, and that you made it open source, just please call it something else.

Please don't call it JSON. Actually I don't care much, as your project will be shunned. The first rule of JSON is that JSON doesn't change.

Douglas built the JSON spec 1) to be language agnostic. Following ES5's syntax directions is fine for ES5 focused development, possibly not for others. 2) to be final - i.e.…

JSON is an amazing serialization format but hand-written JSON is completely wrong. I think this fixes most of the problems of using it in hand-written situations. Just the lack…

I won't begrudge someone a fun little personal project, however (almost) no-one will ever adopt this. It removes too many benefits of JSON/introduces drawbacks for very little…

JSON is wonderful because it is simple and unambiguous. It just works, and serialized data will always look the same. This "JSON5" thing is an abomination. Use whatever quotes…

Three things: * Comments in JSON files are not a great idea because people might (will?) abuse them to add special instructions for their own serializers. As soon as this happens…

Congratulations, you've made something which looks superficially like JSON, but most documents won't parse in 99.9% of JSON parsers. Interoperability is lost, nothing is gained!

Please, don't call it JSON. There is only one JSON, and you didn't make it. It's cool that you made this, and that you made it open source, just please call it something else.

Please rename your project or take it down. People here gave you enough reasons.

I have to agree with most of the criticism in this thread. The lack of comments, strict quoting, no trailing slashes - these aren't problems to fix they are features. As others…

Seems like you're getting a lot of criticism for this, a lot of which I have to agree with. Writing valid JSON is extremely simple and unfortunately it's hard to see how this…

That's npm, not node itself, that relies on package.json. When its creator chose it, he knew exactly what JSON is. He's maintained on HN and elsewhere that he made a good…

Can I ask why YAML wasn't good enough?

This entirely misses the point of JSON. if you want these features it's perfectly acceptable to use YAML instead of JSON.

I absolutely hate hand-writing JSON, but that's why I use YAML. I think you should push for a properly documented subset of YAML, or a full YAML parser in JavaScript instead.…

Can I ask why YAML wasn't good enough?

JSON 3 here: https://github.com/bestiejs/json3

You know that something has gone very deeply wrong somewhere when people oppose your project because they are ideologically opposed to comments. In my own experience, finding out…

Douglas built the JSON spec 1) to be language agnostic. Following ES5's syntax directions is fine for ES5 focused development, possibly not for others. 2) to be final - i.e.…