That criticism feels weak to me outside of the scope of "StrictYaml vs TOML". Within that context, I might agree, having just heard of StrictYaml today. Having dealt with the full blast of complexity YAML and especially XML and XML Schema has in store... TOML is probably one of the top 2-3 config languages I'd use.

I find the friction with deep hierarchical data to be a benefit of TOML as a configuration file. You shouldn't have deep hierarchies in your configs.

I don't like TOML either, but it's lame to derail a topic like this.

that ship sailed.

toml is a prominent example of the least-worst option gaining traction. For configuration files that need to be human editable, provide comments, but are machine readable and have broad support, TOML is the choice that the plurality has settled on. In python, it’s in core tools like pip; it’s not going away because we don’t like how you nest collections awkwardly or whatever.

at least it’s Norway YAML!

The fact that the article complains about the static typing in TOML makes me disregard the entire piece. That's the best part of TOML. I've encountered countless bugs in Ansible because it does know if no is "no" or false.