3 ms·
I actually disagree it's bike shedding. If you can write a bad YAML document because of those mis-features/edge cases, I'd say you've already lost. Humans are
by spicybright 5y ago
I actually disagree it's bike shedding.
If you can write a bad YAML document because of those mis-features/edge cases, I'd say you've already lost.
Humans are messy, but at the end of the day the data has to go to a program, so a concise and super simple interface has a lot of power to it for humans.
Working at a typical software company with average skill level engineers (including myself), no one likes writing YAML. But everyone is fine with JSON.
I think it's a case of conceptual purity vs what an average engineer would actually want to use. And JSON wins that. If YAML was really better than JSON, we'd all be using that right now.
So does it really matter if YAML is superior if >80% of engineers pick JSON instead?
- nine_k 5y agoI'd say that YAML is anything but conceptually pure, with all the arbitrariness, multitude of formattin options, and parsig magic happening without warning. If you want conceptual purity (and far fewer footguns), take Dhall.
- speleding 5y agoI would argue that you can write something poor and/or confusing in any markup language that is sufficiently powerful. Conversely, if a markup language is strict enough to prevent every inconsistency, then it's not powerful enough or too cumbersome to use to be generally useful.