>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

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

If that site lists all the complains that nitpickers managed to put together, it sounds like YAML is virtually perfect.

Also, to underline how silly and futile these nitpicking complains are, some YAML parsers already explicitly address silly things like the Norway problem.

This has literally never been a problem for me despite writing considerable amounts of YAML.

Frankly, this is a phantom benefit: the first thing people do in brackety-languages is define an indent standard. And it's not like a brackety language magically saves you from mis-nesting things if a bracket ends up misplaced.

just the No string is that it? Other than that I've never encoutered any other problem.

> 2-3 levels deep.

Same to python, all non-trivial code is like 4 level+ depth, big deal!

I normally write javascript and I switch to python easily from time to time. I cannot understand people who complain about spaces.