This is definitely a failing of yaml. Though, I feel that generally it’s the sort of thing you learn once the hard way, then it sticks with you pretty well.
Also I’m glad there are more anti-toml folks are out there, feels like I’m taking crazy pills when people say it is “simple” and “elegant”. IMO it’s uglier than old-school ini format - at least it’s more strictly defined but that doesn’t really sway me to convert
elegant, human readable, indentation sensitive language that’s great for deep nesting but has some weird idiosyncrasies with some dynamically typed parsers being too smart for their own good
YAML would such a nice language for config files but then it turns out that “no” is falsy and so a list of Scandinavian countries turns from
into
I wish there was like a JSON5 equivalent for YAML that just reduces its scope lol
(and no, TOML also looks ugly :P)
Norway is false and Finland isn’t in Scandinavia
S W E D E N
S W E D E N
S W E D E N
This is definitely a failing of yaml. Though, I feel that generally it’s the sort of thing you learn once the hard way, then it sticks with you pretty well.
Also I’m glad there are more anti-toml folks are out there, feels like I’m taking crazy pills when people say it is “simple” and “elegant”. IMO it’s uglier than old-school ini format - at least it’s more strictly defined but that doesn’t really sway me to convert
TOML isn’t elegant at all but damn, it is really simple.
Which is better for structured data?
The choice is clear
If by simple you mean “can’t count from 1 to 10 in a loop” and by elegant you mean “easier to understand than a one line perl script” then sure…
You’re looking for StrictYaml