I agree about JSON, but I can't say I understand the logic behind TOML.
I know it's supposed to be a config format, but it only seems to make any sense for INI-like configs that are little more than a flat key-value map.
The places I see people using JSON/YAML/etc for config are much more likely to have nested structures that would be extremely awkward to represent in TOML. I think YAML was on the right track, and if you ignore the messier parts of the spec it works pretty well.
I was mainly using TOML as an example of a config format in contrast to JSON, I wouldn't say it's definitely the answer. Nesting is possible with TOML, but I'd agree that it could get pretty awkward depending on your needs: https://github.com/toml-lang/toml#array-of-tables for example.
I personally don't mind YAML all that much either, although the spec is pretty large.
I know it's supposed to be a config format, but it only seems to make any sense for INI-like configs that are little more than a flat key-value map.
The places I see people using JSON/YAML/etc for config are much more likely to have nested structures that would be extremely awkward to represent in TOML. I think YAML was on the right track, and if you ignore the messier parts of the spec it works pretty well.