[1] https://www.json.org/json-en.html
Saying that all formats have edge cases as an excuse for YAML's glaring faults is, frankly, a cop out. Like if a bridge collapses when a leaf lands on it and saying, well, all bridges have some maximum load. Yes, but in this case it's so bad it's just not useful for anything.
What does the length of the JSON spec have to do with my comment? The parent comment says if you don’t read all your docs you will be bit by an innocuous bug. You linked to a short spec, but that doesn’t mean anything in this context.
> Like if a bridge collapses when a leaf lands on it and saying, well, all bridges have some maximum load.
Is that what you got from reading my comment or the article? Is that what yaml is like?
More specifically, I missed the first line of their comment: "Are people not even reading about what they are using?" If you miss off that line, then it sounds (to me) that they're arguing YAML is a terrible format. With that line, it turns out they think it's reasonable, so long as you read the (huge) spec first. Madness!
A couple of years ago I looked at tutorials and found it very confusing, but the spec is just great.