2 ms·
JSON is a data format. You actually want strict formalism in a data format, because the integrity of the data matters more than flexibility. Comments would onl
by 0xbadcafebee 6y ago
JSON is a data format. You actually want strict formalism in a data format, because the integrity of the data matters more than flexibility.
Comments would only serve to make humans edit the file by hand more than they do now, and to maintain it like a snowflake. You should not be maintaining your data in JSON, it should only be a momentary stop along the way to a more robust data storage system [with a schema].
Optional end commas would only encourage people to use shitty hacks to try to craft JSON without a real parser or encoder, which would 1000% end up with broken JSON all the time, which would then force vendors to support shitty broken JSON.
There's a reason it's designed like it is. Cutting corners is not going to result in better outcomes.