4 ms·
The problem came with E.E I think.. You have to edit like 10 XML files before even getting to the source code files. Granted with today's JS tooling we approach
by rawoke083600 8y ago
The problem came with E.E I think.. You have to edit like 10 XML files before even getting to the source code files. Granted with today's JS tooling we approaching that again :(
- pjmlp 8y agoWithout the static typing and IDE completion support thanks to XML Schema. I will take XML over JSON every time I am the one setting the rules.
- arethuza 8y agoMost editors I use (e.g. Visual Studio Code) provide validation and completion of JSON using JSON Schema - which works pretty well. I much prefer JSON to XML for most scenarios.
- pjmlp 8y agoHow do you validate comment locations?
- arethuza 8y agoWell, as JSON doesn't have comments that's not really a problem :-) NB Not having comments is perhaps the biggest problem I have with JSON when it is used for things like configuration files that will be hand crafted. 99% of the JSON I work with is generated and consumed programmatically so comments aren't really an issue.
- jstimpfle 8y agoMy favourite way to go about comments is to have them inline, as first class data members. (Not that I think either JSON or XML are good ideas. Hierarchical structures are really hard to handle).
- qwerty456127 8y agoIsn't it very easy to add comments support to JSON? Why not just agree to allow /* ... */ anywhere inside it and add this feature to JSON parsers? Honestly I didn't even knew this is not supported to the moment. If nobody bothered so far, doesn't this mean only a tiny portion of people needs this?