XML is a bit verbose but otherwise easy to understand. JSON5 supports comments.
And neither requires me to explain weird formatting nuances to devops engineers.
YAML is a pain to read (lists of structures are very messy), can’t be auto-formatted, and is full of weird “gotchas” (Norway, errant tabs, etc.) if you don’t do things “the right way.”
Requiring the use of whitespace in formatting is wrong. End of.
XML is a bit verbose but otherwise easy to understand. JSON5 supports comments.
And neither requires me to explain weird formatting nuances to devops engineers.
YAML is a pain to read (lists of structures are very messy), can’t be auto-formatted, and is full of weird “gotchas” (Norway, errant tabs, etc.) if you don’t do things “the right way.”
Requiring the use of whitespace in formatting is wrong. End of.
Somebody has to say it, so I’m taking on the duty:
If whitespace is a problem, you use the wrong editor.
Oh, yeah, nothing like telling a dba they’re using the wrong editor when they’re trying to configure something.
If your config format requires specific editors you’re using the wrong format.