Discover the magic of the internet at Imgur, a community powered entertainment destination. Lift your spirits with funny jokes, trending memes, entertaining gifs, inspiring stories, viral videos, and so much more from users.
JSON for serialization all the way. It’s simple and to the point. It does one thing and does it well. There’s little room for annoying surprises. Any JSON can easily be minified and prettified back and forth. If you want it in binary format you can convert it to BSON.
Yaml is too much of a feature creep. It tries to do way too many things at the same time. There are so many traps to fall into if you’re not cautious enough. The same thing can be written in multitudes of ways.
JSON for serialization all the way. It’s simple and to the point. It does one thing and does it well. There’s little room for annoying surprises. Any JSON can easily be minified and prettified back and forth. If you want it in binary format you can convert it to BSON.
Yaml is too much of a feature creep. It tries to do way too many things at the same time. There are so many traps to fall into if you’re not cautious enough. The same thing can be written in multitudes of ways.
Yes, but whoever decided that json can’t have trailing commas has my ire.
{ "a": 1, "b": 2, <-- nope }There was some other pitfall I can’t remember around missing keys and undefined, too, but I can’t remember it now.
Trailing commas are supported in json5, as well as comments
Change to Haskell formatted commas and the problem goes away :D
{ "a": 1 , "b": 2 , "c": [ 3 , 6 , 9 ] }Where is the nearest fire to dump this comment in?
I’m pretty sure you can have trailing commas…
You can’t but some parser allow them. But those that do do not respect the standard.
deleted by creator
There should be a “Simple YAML” that is just scalars, lists, and dicts.
Toml