Who TF is still using XSLT?
Good riddance.
This is a most excellent place for technology news and articles.
Who TF is still using XSLT?
Good riddance.
Chrome's team argues that because only about 0.02% of page loads use XSLT, it's not worth the maintenance burden.
Surely given the volume of browser usage, 0.02% is still a very substantial amount of usage. Lazy fucks
I'm not entirely sure what the "maintenance burden" even is on a tech that hasn't changed in decades.
what burden? I thought burdens don't exist anymore thanks to the power of LLMs???
From the article:
Google says it's removing XSLT to address security vulnerabilities. The underlying library that processes XSLT in Chrome (libxslt) is an aging C/C++ codebase with known memory safety issues. Chrome's team argues that because only about 0.02% of page loads use XSLT, it's not worth the maintenance burden.
It's debatable whether Google, with all its resources, really needs to do this, especially given that 0.02% of all page loads is still quite a lot. But there are certainly times when it's better to just delete seldom-used old code from your project to lower the maintenance burden and the surface area for attacks.
Xslt has nothing to do with RSS being available or not.
It seems to have to do with how it looks formatting wise and not about availability or not, that is what is being meant.
That's just for those few websites that use their RSS feed as their content source. If they want to keep doing that they can just get a JavaScript library that provides XSLT functionality. The feed itself is untouched.
So things like newsbreak who ingest a sites feed then display?
Should be fine. They don't have to use a browser to retrieve that feed.
There are libraries that can polyfill this with almost zero effort. List should not effect any active site that offers rss feeds.