2 ms·
> less human-readable version of JSON Please provide an example, how YAML can be less readable than JSON. I struggle to think of any.
by mystifyingpoi 5mo ago
> less human-readable version of JSON
Please provide an example, how YAML can be less readable than JSON. I struggle to think of any.
- voidUpdate 5mo agoIndentation based structure isn't really a good thing in my eyes, where the format of the document encodes semantic meaning. With JSON, you can display it how you want, and because it's bracketed it will still encode the same data. Also I really don't like the hyphen notation... This is very unreadable to me: - a - b: c - - d
- embedding-shape 5mo agoYAML: - - "hello" YAML expanded: - - "hello" JSON (typical formatting): [ [ "hello" ] ] And EDN for good measure: [["hello"]] I know which one I prefer :) Silly example perhaps, but once you have X lists nested in Y lists, it does become a lot easier to see why some prefer a bit more visually hierarchically stronger syntaxes
- skydhash 5mo agoI still prefer ini files for configuration. Easier to grep and sed.
- beart 5mo agoThey work wonderfully until you need to do anything more advanced than a key-value store.
- skydhash 5mo agoMy belief is that anything that requires more than that are hiding the fact that what they truly need is a DSL. Instead they force you to write AST (ansible, github actions, docker compose,…)
- tracker1 5mo agoYou can get a bit more if you use TOML over INI... it's similar at a baseline, but still a bit more rich for advanced configuration than INI is.