5 ms·
From the repo: > Note the following advantages of RON over JSON: >trailing commas allowed >single- and multi-line comments >field names aren't quoted, so it
by hnarn 3y ago
From the repo:
> Note the following advantages of RON over JSON:
>trailing commas allowed
>single- and multi-line comments
>field names aren't quoted, so it's less verbose
>optional struct names improve readability
>enums are supported (and less verbose than their JSON representation)
I’m no fan of JSON but honestly, I think this is a very weak list of benefits if you’re trying to convince someone to switch.
- rwalle 3y agoAgreed. I don't know why "trailing commas allowed" is a plus -- it is not going to make things simpler or easy to maintain, and it is very questionable whether the added flexibility is worth it
- Tuna-Fish 3y agoHuh? It reduces the logic needed to write the format.
- Tuna-Fish 3y agoThe big reason for potential users is likely this one: > It's designed to support all of Serde's data model