what’s the problem with JSON?
¶ by !undefinedBen Hughes, JSON and the Arguments:
tl;dr: General argument is that JSON is hard to read and the format spec explicitly disallows comments. The former point I disagree with completely; 1 the latter point is fair and/but that’s also why I think something like a Gruntfile is good because it uses functions for configuration (but a Gruntfile is hardly project configuration 2). And/but/so I’m surprised XML wasn’t brought back into this (except in that brief cast-off) because say what you will about XML w/r/t/ verbosity &c. but it’s a hella rich format. 3
- I don’t get it when people say that JSON is hard to read. It’s no more or less hard to read than (say) YAML.[↩]
- I.e., build configuration is not project configuration.[↩]
- Not that I’m a big fan of XML but it is hard to beat if you’re looking for something with rigid, well-defined structures, comments, element-level metadata (e.g., attributes), schemas, validation, etc.[↩]
Leave a Reply