4 ms·
1) Yes, if they're both easy to use, pick JSON - for simplicity's sake. 2) A JSON parser is a far smaller and simpler dependency than an XML parser, especially
by gridlockd 8y ago
1) Yes, if they're both easy to use, pick JSON - for simplicity's sake.
2) A JSON parser is a far smaller and simpler dependency than an XML parser, especially when we're adding XPath to the mix.
3) XML isn't necessarily hard, it's tedious.
4) There's plenty of legacy software out there using all kinds of stuff for config. You don't see a lot of people choosing XML these days. You see YAML or TOML or JSON, even though all of these have issues of their own. JSON happens to be the simplest and most commonly supported.