I think the only alternative to JSON for optimization would be to use a byte stream with data structures in bytes, and compressed using some compression algorithm on that data. But HTTP is not really meant to transfer binary data, so we don't use that on the web.

JSON is actually more compact than XML, which is what we used before JSON. Or worse yet, SOAP. I posted this as a reply to someone else, but here are two documents that represent the same data, one done in SOAP and the other one in JSON.

Which one do you prefer?

@enigmatico #JSON.

I think the problem isn't quite that simple, because most of the issues with #XML are representational.

Consider #SXML-like equivalents for #MathML https://en.wikipedia.org/wiki/MathML#Content_MathML

A Plist is even shorter and simpler a representation than JSON objects.

#SExp #SExpressions

MathML - Wikipedia