6 ms·
* JSON doesn't have comments. I could stop right there because that's a total deal-breaker for me for anything that's supposed to be read or written by humans.
by danmur 3y ago
* JSON doesn't have comments. I could stop right there because that's a total deal-breaker for me for anything that's supposed to be read or written by humans.
* JSON doesn't handle multiline strings.
* JSON is not especially readable (no structure enforced, braces and double quote mandatory).
* JSON can't load YAML but YAML can load JSON.
(lots more)
- deafpolygon 3y agoGiven this, I'd much rather XML any day. You can comment using <!-- Comment --> blocks.
- danmur 3y agoI have zero problems with XML. Hard sell though. It's annoying though because it's so mature compared to everything similar (even YAML, which I obviously quite like); like if you make an XSD for your config files everyone gets free editing features (not just validation, completion as well, even completion of attributes)
- vaylian 3y agoNo trailing commas makes editing JSON a pain
- thaumasiotes 3y agoThe lack of trailing commas isn't the problem. The problem is the intermediary commas. Those are used in JavaScript to give you the option to provide an expression in place of a single term. But that's not even allowed in JSON, so the commas aren't serving any purpose at all.