The proposed modifications are utterly trivial and don't really make anyone's life better.
The proposed modifications are utterly trivial and don't really make anyone's life better.
As a side note, negativity for the sake of being negative does not help the conversation at all. Please take that kind of attitude somewhere else.
These are poor modifications. Don't modify JSON to be a better configuration format, just use a better format.
Rather hard to do when the rest of the world you need to interact wouldn't necessarily move with you.
Hand-hackability and simplicity is why we use JSON. These changes definitely make things better for humans.
So this proposal is coming back and fixing that silly limitation.
That is, if you really want comments, crockford says, go ahead and add them. Just remember to remove them before parsing as JSON. Which is actually not that hard. you can even do it with sed. Just for the love of crock don't put processing directives in the comments.
What?? By that logic, you might as well hand-write x86 assembly, since C requires a "preprocessing" step (some might call that compilation).
Using "JSON5" as a human-writable format for storage and then compiling it to real JSON before going over the wire seems like the best of both worlds to me. The wire format benefits are preserved, the format is validated as a side effect of compilation, and you get to write in a well-defined language with comments and bareword-identifiers. Your objection is that you don't want to run a compiler, so you'd rather send JSON5 over the wire?
> dumb suggestion .. defeats the entire point of having JSON in the first place
No. Json's mission is to be a wire protocol. You're suggesting using it for other purposes, and in a way that compromises its role here as a wire protocol. It's not intended to be a multi-purpose serialisation format.