2 ms·
Using JSON for configuration was and continues to be a terrible blunder. TOML fills that role wonderfully. And it isn’t full of complexity that turns Yaml into
by Waterluvian 3y ago
Using JSON for configuration was and continues to be a terrible blunder.
TOML fills that role wonderfully. And it isn’t full of complexity that turns Yaml into a mess.
- eviks 3y agoBad nesting alone would make it a similar blunder for configuration
- shaunpersad 3y agoI've had the complete opposite experience. Neither YAML or TOML are very obvious to me. I always have to double and triple check that my syntax does what I assume it will do. I never have that problem with JSON.
- Waterluvian 3y agoNot adding comments to a config file is recipe for complete disaster. You can kinda fake it but it’s just a silly headache. Which is recognized given there’s now “JSONC” but now you’ve got even more confusion determining what systems can actually accept comments or not. That’s always fun. I’m curious what parts of TOML do people find confusing? It’s such a tiny markup language.