Re:OPML Is Underrated
by chriswarbo on Saturday February 10, 2024 @11:55AM
(#39327804)
Resource requirements expand until it they hit a user-noticable limit. Even ultra-compressed every-bit-counts encodings[0] would be ignored and abused until they're bloated to a user-noticable limit. Or the extra bandwidth would be used for more video ads.
> 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 feel like most web applications today make hundreds of HTTP requests when opening them. If that's acceptable, then XML vs. JSON doesn't matter.
XML is definitely more verbose than JSON, though I'd be very surprised if an average content-heavy site would be smaller with something like JSON + react. I'd be surprised if server components tipped the scales either given that the server state would still be shipped as HTML and/or a virtual dom representation.
Re:OPML Is Underrated
by cryptonector on Saturday February 10, 2024 @05:55PM
(#39330989)
FastInfoSet enters the chat
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.
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.