Obviously JSON isn't well optimized either but I wonder how much, if any, progress might have been slowed by XML syntax clogging the pipes even more.
> how much, if any, progress might have been slowed by XML syntax clogging the pipes even more.
Depends what you mean by "progress", and if you think Web development has been improving or devolving over time.
[0]https://www.microsoft.com/en-us/research/publication/functio...
I.e., you can have XML and have it be compact by serializing it to something very close to ASN.1's PER (packed encoding rules).
Ditto for JSON, though there's lots of competing binary JSON schemes out there.
Maybe any time we create a new serialization scheme we should create an ETL for it.
Or maybe we shouldn't create new serialization schemes all the time. Here's just a few of them, and that's rather many: https://en.wikipedia.org/wiki/Comparison_of_data-serializati...
Maybe we should require licensure for creating new serialization schemes :)
People are starting to realize that most sites really boil down to parsing server state and rendering DOM. We never needed to do all this nonsense with serializing all state to JSON and shipping the entire rendering pipeline to the browser, that was just a heavy handed solution for a very specific scaling issue at Facebook.