←back to thread

XSLT – Native, zero-config build system for the Web

(github.com)
392 points _kush | 3 comments | 27 Jun 25 05:00 UTC | HN request time: 0s | source
Show context
fergie ◴[27 Jun 25 07:09 UTC] No.44394408[source]▶
What is this "XSLT works natively in the browser" sourcery? The last time I used XSLT was like 20 years ago- but I used it A LOT, FOR YEARS. In those days you needed a massive wobbly tower of enterprise Java to make it work which sort of detracted from the elegance of XSLT itself. But if XSLT actually works in the browser- has the holy grail of host-anywhere static templating actually been sitting under our noses this whole time?
replies(10): >>44394475 #>>44394896 #>>44395079 #>>44395141 #>>44395223 #>>44395594 #>>44396076 #>>44396139 #>>44397002 #>>44399078 #
1. Symbiote ◴[27 Jun 25 07:21 UTC] No.44394475[source]▶
I worked with a site using XSLT in the browser in 2008, but I think support goes back to the early 2000s.
replies(1): >>44394542 #
2. fergie ◴[27 Jun 25 07:31 UTC] No.44394542[source]▶
I was _really_ deep into XSLT- I even wrote the XSLT 2 parser for Wikipedia in like 2009, so I'm not sure why I haven't been aware of browser native support for transformations until now. Or maybe I was and I just forgot.
replies(1): >>44395534 #
3. rjsw ◴[27 Jun 25 10:18 UTC] No.44395534[source]▶
It was a feature of IE5.

I updated an XSLT system to work with then latest Firefox a couple of years ago. We have scripts in a different directory to the documents being transformed which requires a security setting to be changed in Firefox to make it work, I don't know if an equivalent thing is needed for Chrome.