If there are no humans in the loop, sure, like for data transfer. But for, e.g., configuration files, i'd prefer a text-based solution instead of a binary one, JSON is a nice fit.

[–] Michal@programming.dev 0 points 2 years ago (2 children)

Yaml is more human readable/editable, and it's a superset of json!

[–] bitfucker@programming.dev 1 points 2 years ago

Until someone cannot tell the difference between tab and space when configuring or you miss one indentation. Seriously, whoever thinks indentation should have semantic meaning for computers should burn in hell. Indentation is for us, humans, not computers. You can write a JSON with or without indentation if you want. Also, use JSON5 to have comments and other good stuff for a config file.

[–] bob_lemon@feddit.org 1 points 2 years ago

Yaml is just arcane bullshit to actually write as a human. Nor is it intuitively clear how yaml serializes.

[–] bleistift2@sopuli.xyz 1 points 2 years ago

Hell, no. If I wanted to save bytes, I’d use a binary format, or just fucking zip the JSON. Looking at a request-response pair and quickly understanding the transferred data is invaluable.

[–] wtfrank@feddit.uk 0 points 2 years ago (1 children)

Yaml?

[–] JackbyDev@programming.dev 0 points 2 years ago (1 children)

For the love of all things pure, holy, and just, please do not use YAML in your APIs...

[–] wtfrank@feddit.uk 0 points 2 years ago (1 children)

Fine, and if you don't use json in your API because of the deficiency highlighted in the meme, what format do you use in your API?

[–] JackbyDev@programming.dev 1 points 2 years ago

I use JSON. I have used Avro for things in Kafka but I'm not sure the benefits outweigh the negatives. Avro is much more complicated than people think and most folks don't really have a strong desire to learn how it should be used and do stuff incorrectly. Everybody knows JSON and it works with everything though. (Example: so many people just hear that Avro schemas can be backwards compatible but have zero idea that you still need the schema that wrote the message even if you want to read it into a newer one.)

Interestingly, I take the meme as saying a dev is using the wrong types in their serialization format (using strings to store integers) which was my biggest problem with Avro. Mostly from people not using logical types or preferring to use ISO 8601 datetime strings instead of the built-in timestamp-millis type.