3 ms·
I think it's pretty much a dead technology now, except for legacy uses like in big XML-heavy Java frameworks that were early adopters. I've tried using it for d
by roel_v 17y ago
I think it's pretty much a dead technology now, except for legacy uses like in big XML-heavy Java frameworks that were early adopters. I've tried using it for document transformation purposes several times but never found a use where it wasn't easier to just write a DOM-manipulating script. As a templating system I don't see any advantages either - conceptually it's nice to force the separation of programming logic and templating functionality, but then again, you soon need similar constructs (if, loops, includes, ...) anyway and then you have to switch to xslt extension libraries... When it comes to templating, I still much prefer showing programmer constraint is a better way to go than technical barriers. That tradeoff may be different in a context where you have dozens of programmers/designers/content producers work on a site. But for a site of that size performance would presumably exclude XSLT.
In general, I get the impression that the 'XML everywhere' fad has passed and that technologies like XSLT, xsl:fo and the myriad of xml replacements for DTD's have passed their peak a few years ago.
- Eldila2 17y agoI totally agree. In a previous job, we had a system that used XSLT to generate the public website. I never really cared for it. The language seemed very verbose and you can do the same thing in other languages more simply. I think xsl:fo still has some uses when generating dynamic pdfs. Other than that, I would stay away from it if you could.
- yesimahuman 17y agoYes, it is definitely being used in some very large and prominent applications, but in my experience the developers and management are aware of the deficiencies and want to move past it (but this takes a long time). I don't see a need either to start learning it now, unless you happen to go work for one of these companies that use it extensively. Ultimately it always seemed to me like it was a tool to deal with the non-uniform hacky XML data the company had literally everywhere. Perhaps that's the problem that needs to be fixed.
- borisk 17y agoRight, not worth learning it now. BTW Blizzard uses in-browser XSLT on most of their sites - http://extremelyxslt.blogspot.com/2008/07/world-of-xslt-craft-aka-world-of.html http://extremelyxslt.blogspot.com/2008/07/world-of-xslt-craf...