Hacker News new | ask | show | jobs
by scotty79 533 days ago
I think webapps should be xml (with all the data to display) transformed into html on the client side with XSLT generated by framework templating system).

There's a really nice binary XML format that browsers haven't implemented yet: https://en.m.wikipedia.org/wiki/Efficient_XML_Interchange

3 comments

Symphony CMS [1] was based on this idea over a decade ago.

The developer experience was amazing, you could easily inspect the data backing any page. XSLT was hard but probably easier than React these days.

[1] https://getsymphony.com

What a blast from the past. We did exactly this in '99-2000 (yes), and it was ridiculed as being over-engineered. At the time, it was the future because "XML will underpin all data transfer everywhere", and therefore we would be set up to run on any device, should any other device begin to exist. Needless to say, the winds changed way sooner than that became a real use case.
I originally had this idea about 20 years ago. I still think it's good. At least better than brotli compressed json loaded with JavaScript.
How would such a webapp make API calls and act on the responses? Even for a static website, HTML isn't very good at handling arbitrary sizes, which I think was part of the original motivation for React.