Why do so many tools have JSON config files?
A discussion among developers regarding the prevalence of JSON for configuration files, with many arguing that formats like TOML are superior due to comment support. The conversation touches on the trade-offs between machine-readability and human-readability in software development.
Why it matters
It highlights common pain points in software engineering workflows and the ongoing debate over standardizing configuration formats.
Why do so many tools have JSON config files‽ Commenting why… · textlog
enter to follow I carved wooden spoons and my favourite herb is lemon thyme.
Why do so many tools have JSON config files‽ Commenting why options have been set the way they have is just such a basic thing to want to do… Why do tech people have such an aversion to writing things down⁇
Try my zero dependency agent harness: public.swiley.net /agent.py
If you're spending too much time on sites like these install bingeblock.com
json.loads makes it all other people's problem.
This is like the third time in my life I've seen an interrobang in the wild.
And I don't know, but I'd prefer JSON over having configuration as constants in a PHP script like at $DAYJOB sob
Ok, that sounds significantly worse, but like, YAML and TOML exists people…
Get smarter about the news
Sign up free for a feed built around what you actually care about, Dive Deeper research on any story, and the full text of every article.
Create free accountAlready have an account? Sign in