What is this TOML?Visualizer:https://toml-to-json.orchard.blog/Code:https://github.com/orcharddweller/toml-to-jsonTOML spec:https://toml.io/en/v1.0.0#TOML #t...
Because no one ever uses those. Literally > and | are the only ones I’ve ever seen in over a decade and you will never need to worry about the differences between the two.
XML as a configuration language is terrible. Yaml gets the point across in an easily readable way, which is exactly the point. Same for JSON except JSON you can’t even use comments (you need json5 or one of the numerous other alternatives to get those).
It’s really unfortunate the devops world chose such a hot mess of a format. JSONC would be a dumb choice and still do a better job for most config files.
Wow. I’ve never used yaml or even looked at it but damn that is horrid. Why do people even use this? JSON and XML are so better.
Because no one ever uses those. Literally
>
and|
are the only ones I’ve ever seen in over a decade and you will never need to worry about the differences between the two.XML as a configuration language is terrible. Yaml gets the point across in an easily readable way, which is exactly the point. Same for JSON except JSON you can’t even use comments (you need json5 or one of the numerous other alternatives to get those).
I say this with all due respect, but XML can gargle nuts.
It’s really unfortunate the devops world chose such a hot mess of a format. JSONC would be a dumb choice and still do a better job for most config files.
noyaml.com