There are several fundamental problems with JSON, one of which being that you have to duplicate the field names over and over again. It's just not a very structured format. Trailing commas is the least of my concerns.
I would like to see protobuf take over at this point.
You can't edit a protobufs in an editor.
There's a canonical JSON serialisation in v3 as well, although obviously that doesn't solve the OP's problem...
[1] RFC-7049, also http://cbor.io/
[2] http://cbor.schmorp.de/stringref It won't make much sense unless you already understand CBOR encoding, but it's a registered extension.
As a storage format I don't like it, either. No canonical representation (at all): Arbitrary whitespace, arbitrary order of members. Too much line noise: Quotes around each member name. No schema support.
You'd be surprised -- if you had to live through the XML madness of the early 00s. And don't get me started on SOAP, XML namespaces and other crap.
>There are several fundamental problems with JSON, one of which being that you have to duplicate the field names over and over again.
You don't duplicate field names. You define different objects that just happen to have the same fields. They could just as well have different ones.
That's something for transport compression to handle.
{
'fields': ['a', 'b'],
'values': [
[1, 2],
[5, true]
]
} {
a: [1, 2],
b: [5, true],
}