Actually, after finding out about TOML[1], I would suggest to look at it. It is a lot simpler than YAML, explicitly does not support dangerous features like deserializing arbitrary data structures, while being very readable. Spec is not entirely stable yet, though.
Agreed. After using both YAML and TOML, I'd say that TOML is much more readable as compared to YAML.
TOML does indeed look good, reminds me of a extended .ini format
Re:JSON vs. YAML – try it yourself
by lfender6445 on Tuesday April 07, 2015 @11:35PM
(#9338662)
can you give me dumbed down example of 'deserializing arbitrary data structures' not sure i follow
Re:JSON vs. YAML – try it yourself
by joelthelion on Tuesday April 07, 2015 @03:15AM
(#9332426)
We don't need two different languages for this.
Oh, yes, we do. We need a language targeted at humans that is machines can
process and we need a language targeted at machine processing that is
inspectable by humans. Those are two contradicting targets: the latter calls
for simplicity, but the former calls for shortcuts[#] to make human's work
easier, which adds, not reduces, complexity.
[#] Shortcuts like not quoting keys and omitting braces and commas in hash definition.
Json intentionally does not support comments. Think about that for a bit and you'll realise what Json is for and what it isn't for.
As SeoxyS said: use yaml for config files, Json for APIs.