urquell,

So much json here. All wrong, it’s csv

magic_lobster_party,

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.

interolivary,
@interolivary@beehaw.org avatar

There’s a special place in hell for the inventor of semantically significant whitespace.

YAML itself is one of the circles of hell. You have to copy-paste YAML from web etc sources with dubious formatting for all eternity, and the editor doesn’t have YAML support. Also you can only use Python

synae,
@synae@lemmy.sdf.org avatar

For serializing? I’d probably just go with json.

For content meant to be written or edited by humans? YAML all day baby

nxdefiant,

If you have a choice to start from scratch, TOML is probably the better option.

suy,

Norway.

Ups. Sorry, I meant “NO”.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • programmer_humor@programming.dev
  • localhost
  • All magazines
  • Loading…
    Loading the web debug toolbar…
    Attempt #