[mystifyingpoi]

> 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]

Indentation 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]

YAML:

  - - "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]

I still prefer ini files for configuration. Easier to grep and sed.

[tracker1]

You 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.

[beart]

They work wonderfully until you need to do anything more advanced than a key-value store.

[skydhash]

My 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,…)