Is CBOR as popularly supported as JSON?
Also, to answer your question with a guess, I would suppose it’s because they wanted to use JSON and they wrote the feature.
Also, to answer your question with a guess, I would suppose it’s because they wanted to use JSON and they wrote the feature.
UTF-8 is already a great wire format.
I've never found a "binary JSON" that's significantly better than this; I mean you can beat it, but you need awkward encodings (prefix indices & other weird shit). You end up burning nearly-byte for any particularly clever integer encoding.
Most data structures are just nested arrays of integers. If you need an integer keyed OBJECT you're SOL, but I just play fiddly games with astral plane UTF-8 characters. (Yeah yeah yeah ad hoc encodings are nasty news.)
If you've got a BUTT LOAD of data just fire up a compressing SQLite DB like a normal human.