This just seems to fix problems for the lazy or those that lack architectural rigidity in their development patterns.
JSON is a data encapsulation format that doesn't care about the data contained within. That is up for your programs to consume and decide.
If you think JSON needs "more" like comments, parsing, multi-line, etc. then perhaps you need to revisit your architecture.
If you disagree I am sure there are plenty of frameworks out there that will babysit your data and document things for you. But upsetting the core apple cart here would be a huge mistake.
The support for numeric Infinity is basically the one unabashedly-semantic modification; it doesn't go far enough, though, since it should be possible to serialize any float, valid or invalid, in a data-exchange format. I'd think proper support would involve a Rational representation--encoding Infinity as, say, 1/0.
So anyone that picked JSON as a configuration format needs to revisit their architecture? At the moment, yes. But if comments had not been forbidden then things would be just fine.
JSON is a data encapsulation format that doesn't care about the data contained within. That is up for your programs to consume and decide.
If you think JSON needs "more" like comments, parsing, multi-line, etc. then perhaps you need to revisit your architecture.
If you disagree I am sure there are plenty of frameworks out there that will babysit your data and document things for you. But upsetting the core apple cart here would be a huge mistake.