JSON vs Alternatives
Discussions debate the strengths and limitations of JSON as a data format for exchange, configuration, and serialization, often defending it against alternatives like YAML, TOML, or new human-friendly proposals.
Activity Over Time
Top Contributors
Keywords
Sample Comments
Why not just use JSON until you've got a compelling reason not to?
JSON isn't just about human readability, it's about being a 'good enough' standard for data exchange. What binary format would you use that people could parse as reliably as JSON?
It's JSON with some syntactical sugar. Is that really so bad?
I read some samples, how is this better than good ol JSON?
I agree, same reason people use json in the first place despite the inefficiency, it's easier.
Can you tell me what was the context that lead you to create this?Unrelated JSON experience:I worked on a serializer which save/load json files as well as binary file (using a common interface).From my own use case I found JSON to be restrictive for no benefit (because I don't use it in a Javascript ecosystem)So I change the json format into something way more lax (optional comma, optional colon, optional quotes, multi line string, comments).I wish we would stop pretendi
JSON is great for a lot of things, but sometimes CSV is better. Sometimes packed binary is better. JSON for all things is a bad plan.
Json is just a format. There are trillions of formats that work just as well as json.
one reason why JSON is superior to things like TOML or YAML for these use-cases...
Sure, its okay. But compared to the ease of JSON...