Re:JSON as configuration files: please don’t (2016)
by thechao on Saturday April 13, 2019 @02:35PM
(#19654850)
I find it interesting you're being downvoted. I think your question is reasonable: why does XML suck "harder" than JSON? This just seems a bit faddish to me. Things like namespaces and attribute/child distinction in XML are super annoying ... until you really need them in your ML (JSON, in this case). Then, suddenly, you're reinventing a wheel, hoping all of your downstream tools 'agree' on the behavior.
[ Parent
| on HN ]
Re:JSON as configuration files: please don’t (2016)
by Thiez on Saturday April 13, 2019 @02:49PM
(#19654962)
The votes seem to be going the other way now :-)
I've heard people prefer JSON over XML because XML is too complex... and now we have json schemas, jsonpath... the namespaces can't be far away.
I'll admit that XML probably would be better without entities and the crazy whitespace handling.
Re:JSON as configuration files: please don’t (2016)
by joezydeco on Saturday April 13, 2019 @06:02PM
(#19656020)
Why does it suck harder? I’ll give one example: arrays.
In JSON they’re plain and simple. You even get to use good ‘ol [ ] delimiters.
In XML? It’s a sea of open and close tags.
Now do an array of arrays. Then hand-edit it.
Like I said, it’s no better. But it’s way easier to read.