6 ms·
>I was really into XSLT at the time :) We all have embarasing skeletons in our closets, and that's one of mine, too. https://news.ycombinator.com/item?id=3372
by DonHopkins 3y ago
>I was really into XSLT at the time :)
We all have embarasing skeletons in our closets, and that's one of mine, too.
https://news.ycombinator.com/item?id=33728303 https://news.ycombinator.com/item?id=33728303
>My impression of XSLT is that there were representatives from every different programming language paradigm on the XSLT standard committee, and each one of them was able to get just enough of what was special about their own paradigm into the standard to showcase it while sabotaging the others and making them all look foolish, but not enough to actually get any work done or lord forbid synergistically dovetail together into a unified whole.
>The only way I was ever able to get anything done with XLST was to use Microsoft's script extensions to drop down into JavaScript and just solve the problem with a few lines of code. And that begs the question of why am I not just solving this problem with a few lines of JavaScript code instead of inviting XSLT to the party?
- schemescape 3y agoI can’t decide if I liked XSLT or just the out-of-the-box thinking its convoluted solutions demanded. XPath was a joy to use, and I thought XHTML made more sense than HTML. But I was naive to think the “more logical” technology would take over!
- jrumbut 3y agoThere is a unique satisfaction to solving a problem with XSLT. That said, it's a lot like that old joke about regular expressions, "now you have two problems."
- pjmlp 3y agoI am on the same boat. In fact, our own take on AOLServer used xml namespaces for our widget libraries, but alas we got HTML 5 instead, and Web Components are still not widely adopted.