51–60 of 199 posts
Earlier quoted context omitted.
This sucks, because it limits the usability of JSON. It should interfere with its being a serialization and interchange format, but for configuration files anything without comments is useless.
https://plus.google.com/118095276221607585885/posts/RK8qyGVa...
What's so awesome about JSON? Its standard documentation is 5 pages. So simple, so awesome.
Does this mean we can now use it for evil?
Hilarious! ECMA-404. My neighbor's address is 404 West Whatever Street and I can't look at their mailbox without wondering if mail is correctly delivered there...
My faint hopes for trailing comma support are now crushed.
What does trailing comma support get you?
JSON is a great way to make your data accessible to deep packet scanning systems. Define all your protocols with JSON!
They say JSON is not for binary and won't change. With a backslash (oops reverse solidus) you could send binary data - eg an image. { myimage: "\01\02\03" } of course, not efficient. You could base64-encode it and put that in a string. I think some syntax for binary would be useful - eg { myimage: 0x010203 }
The slash and the solidus are two separate entities. I am not aware of any use of the actual solidus being used for escaping.
Earlier quoted context omitted.
What does trailing comma support get you?
For large code bases, you don't break git blame by adding in new arguments. And it's one less thing to think about when editing your code: always add a comma, never worry about errors because you need to add a comma to the line above.