Skip to main content


Repeat after me: JSON is not a valid choice for human-editable configuration files.

reshared this

True. JSON files don't even support comments (!!)
@farseen for me it's the main sticking point. what about you, @zhenech ?
The list syntax mandating ,s on all list items, except the last

That kind of violation of postel's law makes it a giant pain for humans
@silverwizard @farseen oh yeah, almost forgot about that
@farseen @silverwizard I've used it, but it's kind of hard to get the syntax right
I am a TOML evangelist who thinks YAML is read-only, writing is beyond finicky ime
@isotopp Python has a lot of nice corners. setup.py is not one of them.
@Kris
Exactly! I mean, who in their right mind would use anything else than deeply nested XML, with liberal use of attributes, namespaces, and unordered serialization when updating it after in-app changes are made?
JSON is not a valid choice for human-editable configuration files.
JSON is not a valid choice for human-editable configuration files.
People who like JSON are obsessed with the idea that XML is bad which is the most annoying thing

1) XML is not as bad as JSON
2) who cares about XML, it's not 2001
JSON is designed to not be readable at a glance and resist quick updates

XML is criticized for being too verbose
Nah, when it is a {,[, or (, and how do you add a thing to a list? What if it's in the middle? What if at the end?

To be clear - if you run JS a lot, JSON makes a lot more sense, but that's an unrelated crime
@silverwizard @quincy @farseen wholesome agree with you, JSON is for machine write/read, yaml is somewhat human readable and TOML +- usable also for human writing
⇧