3 ms·
When you have 70+% browser market share, stopping support for something _is_ killing it.
by itsgrimetime 11mo ago
When you have 70+% browser market share, stopping support for something _is_ killing it.
- eXpl0it3r 11mo agoIt is misleading in so far that XSLT is an independent standard [1] and isn't owned by Google, so they cannot "kill it", or rather they'd have to ask W3C to mark it as deprecated. What they can do is remove support for XSLT in Chrome and thus basically kill XSLT for websites. Which until now I didn't even know was supported and used. XSLT can be used in many other areas as well, e.g. for XSL-FO [2] [1] https://www.w3.org/TR/xslt-30/ https://www.w3.org/TR/xslt-30/ [2] https://en.wikipedia.org/wiki/XSL_Formatting_Objects https://en.wikipedia.org/wiki/XSL_Formatting_Objects
- James_K 11mo agoYou say they cannot kill it, and yet they are about to. We'll see who wins, reality or your word games.
- aaronrobinson 11mo agoWhat are you talking about? They can’t kill it. Most use is outside the browser. It’s not about mixing words.
- mortarion 11mo agoI don't think XSLT was invented for the purpose of rendering XML into HTML in the first place. Perhaps it never should have been introduced in browsers to begin with?
- righthand 11mo agoWrong. Can you dissenters at least provide proof of your nonsense lies? XSLT is apart of the HTML standard.
- aaronrobinson 11mo agoNo it isn’t.
- righthand 11mo agoYes it is loser
- vbezhenar 11mo agoXSLT was invented to transform one XML document to another XML document. Browser can render XHTML which is also a valid XML. So it's pretty natural to use XSLT to convert XML into XHTML which is rendered by browser. Of course you can do it on the server side, but client side support enables some interesting use-cases.
- aaronrobinson 11mo agoAre you aware that XSLT is mostly used outside the browser?