I hate this grug brain writing style. It sounds bad and is hard to read. Please just write normal, full sentences.
Maybe it’s just the way the author writes?
XSLT – Native, zero-config build system for the Web
31–40 of 337 posts
Re: XSLT – Native, zero-config build system for the Web
#32What 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?
Re: XSLT – Native, zero-config build system for the Web
#33Blast from the past. I actually used XSLT quite a bit in the early 00s. Eventually I think everyone figured out XML is an ugly way to write S-expressions.
Re: XSLT – Native, zero-config build system for the Web
#34Ok, so it might be a long shot, but I would say that
1. the browsers were inconsistent in 1990-2000 so we started using JS to make them behave the same
2. meanwhile the only thing we needed were good CSS styles which were not yet present and consistent behaviour
3. over the years the browsers started behaving the same (mainly because Highlander rules - there can be only one, but Firefox is also coping well)
4. but we already got used to having frameworks that would make the pages look the same on all browsers. Also the paradigm was switched to have json data rendered
5. at the current technology we could cope with server generated old-school web pages because they would have low footprint, work faster and require less memory.
Why do I say that? Recently we started working on a migration from a legacy system. Looks like 2000s standard page per HTTP request. Every action like add remove etc. requires a http refresh. However it works much faster than our react system. Because:
1. Nowadays the internet is much faster
2. Phones have a lot of memory which is wasted by js frameworks
3. in the backend all's almost same old story - CRUD CRUD and CRUD (+ pagination, + transactions)
Re: XSLT – Native, zero-config build system for the Web
#35I worked with XSLT almost from the beginning of my career and it was a blessing in disguise. Shoutout to Michael Kay.
Re: XSLT – Native, zero-config build system for the Web
#36me busy fixing asan, "illegal instruction", blah blah blah, me sad and frustrated, much scowling. me come to hn, see xml build system, me happy, much smiling, me hit up arrow, me thank good stranger.
Dear God the writing style on that article
Re: XSLT – Native, zero-config build system for the Web
#37What 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 thi…
I worked with a site using XSLT in the browser in 2008, but I think support goes back to the early 2000s.
Re: XSLT – Native, zero-config build system for the Web
#38> how I can run it? open XML file
> open blog.xml -a Safari
This didn't work for me on my browsers (FF/Chrome/Safari) on Mac, apparently XSLT only works there when accessed through HTTP:
$ python3 -m http.server --directory .
$ open http://localhost:8000/blog.xml
Re: XSLT – Native, zero-config build system for the Web
#39All that fuss just to deploy a static website on Vercel? :p
Re: XSLT – Native, zero-config build system for the Web
#40It's sad how the bloat of '00s enterprise XML made the tech seem outdated and drove everyone to 'cleaner' JSON, because things like XSLT and XPath were very mature and solved a lot of the problems we still struggle with in other formats. I'm probably guilty of some of the bad practice: I have fond memories of (ab)using XSLT includes back in the day with PHP stream wrappers to have stuff like ` ` This may be out-of-da…
Xpath would have been nice if you didnt have to pedantically namespace every bit of every query