3 ms·
Remember XML/XSLT? You were supposed to write your webpage in pure XML -- this way the content was pure, and can be indexed, processed by other programs, etc.
by fortran77 6y ago
Remember XML/XSLT?
You were supposed to write your webpage in pure XML -- this way the content was pure, and can be indexed, processed by other programs, etc. -- and then styled by XSL transformations.
I spent a lot of time learning this. It never caught on. Browsers still support it.
http://xml.silmaril.ie/browsers.html http://xml.silmaril.ie/browsers.html
- majewsky 6y agoOur hackerspace's website is written in XML/XSLT that renders HTML during `make`. I haven't been around when it was built. All I know is that there are only 2 people who know the guts of the XSLT stuff. Everyone else just copy-pastes XML snippets from somewhere else and edits them to publish a new news item or calendar entry. (I don't know how much of that is attributable to XSLT's nature, and how much of it is due to its relative obscurity. But it's certainly not a stack that I would choose for a new website based on that experience.)
- bjoli 6y agoI just style XML directly with CSS. That works fine if you just want to display it in a browser. XSLT can of course do a lot more complex transformations on your data.
- sergeykish 6y agoCould you please share a bit more? I know I can style XML with <style>, it can be handy to make RSS readable - http://feeds.bbci.co.uk/news/rss.xml http://feeds.bbci.co.uk/news/rss.xml Anything else where it shines?
- bjoli 6y agoYou can make any document into a full blown web page. I remember looking at the source of a snappy yet functional web page recently. It was the raw XML output from their code comments with an XML front page. It was all just raw XML and CSS. There is no "time until valid paint". Everything renders when it's done, which means you get a lag before things show up in screen where you otherwise already have things rendering.