The fact that it allows comments is really, really handy. I used to be a JSON advocate until I realized this one useful piece of info.
Comment on A lot of YAML
Michal@programming.dev 1 year agoHow’s it annoying? It’s easier to edit by hand than json as it allows for comments and there’s no trailing comma errors. I prefer it any day over json.
TheGiantKorean@lemmy.world 1 year ago
bellsDoSing@lemm.ee 1 year ago
Yeah, such a simple, but still killer feature. Really sad that JSON doesn’t support them.
TheGiantKorean@lemmy.world 1 year ago
I wonder how you’d even implement that. Like maybe {! At the beginning.
GTG3000@programming.dev 1 year ago
Most comment-aware JSON parsers I’ve seen just use standard // to delineate comment lines.
zalgotext@sh.itjust.works 1 year ago
It’s just another syntax to learn. For someone who already has their head crammed full of a bunch of other syntaxes over the years, I didn’t want to learn a new one. YAML has kind of forced it’s way in anyways though.
magic_lobster_party@kbin.social 1 year ago
There’s a lot of foot guns in YAML. The specification is way more complicated with hidden obscurities. JSON specification is just 5 diagrams. YAML speciation on the other hand is an 86 page pdf, so there’s more room for nasty surprises (which is not a thing you want in configuration files).
I’ve also seen many people struggle more than they need to with the yaml indentation.
I think the only upside to yaml is that it allows for comments, but other than that JSON all the way.
https://ruudvanasseldonk.com/2023/01/11/the-yaml-document-from-hell