Nitpick you wonder why yaml is preferred to ini files when it is lined up to each other.

INI files are not specified anywhere, so it ends up being a implementation-defined free-for-all.

Also, YAML supports data structures that INI files don't.

I don't understand the hate that YAML gets. If you're not tasked with writing a parser, the data format just works as expected.

> I don't understand the hate that YAML gets

https://noyaml.com/ is a decent overview of exactly how shit it is.

But outside of that, using spaces for logic is extremely error prone if you go past 10-15 lines and 2-3 levels deep.

>https://noyaml.com/

I'm not sure this is the criticism you think it is. Wow, so you basically have to add quotes to get strings in some ambiguous situations?

Yeah sure you could probably improve YAML by getting rid of these weird pitfalls, but that is a minor improvement. The alternative isn't something like TOML, because YAML is optimized for hierarchical configuration. It's every vendor implementing a different syntax such as Hashicorp with their HCL [0].

[0] https://github.com/hashicorp/hcl