this post was submitted on 06 Sep 2024
60 points (73.4% liked)
Programming
17145 readers
575 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Yes, they could've just used JSON. Totally pointless waste of time.
JSON does lack comments. And numbers that are not 64 floats.
TFB, the numbers are not defined as 64 bits floats.
They are just not defined. At all.
Exactly that's a job for the parser / consumer.
That's a valid point.
There are two kinds of good serialization languages, the ones where values are black boxes and only serialize the data structure, and the ones where everything is completely determined and can be turned directly into an API.
JSON is neither, but it's closer to the first than YAML. XML is the first, while the SOAP standard almost turns it into the second. TOML is about as close to the first as JSON.
Readability in general sucks
There's a spec for json with comments. It's better than yaml in every way.
And lack of trailing comma's
There's a lot of JSON parsers that don't mind to see comments there, just ignore them. And there's also the "_comment" / "$comment" thing.
So Poe's Law and all that... I really hope you're being sarcastic because having non-technical people hand edit JSON is a nightmare. It's also quite annoying to read without a lot of extra whitespace which most editors that'd help less technical folks omit... and comments to help highlight what different things mean are hacky, hard to read, and actually read as data.
No, I'm kind of serious, the comment situation is already solved in JSON... about the rest yeah, Yaml might be easier but the different isn't that much. Non tech people can't edit Yaml properly either so.