cross-posted from: https://lemmy.bestiver.se/post/555312
My comment: It seems google is trying to pull another Manifest v3 and JPEGXL - propose then ignore everyone and do it anyway.
(tldr: libxslt is a significant source of vulnerabilities and it should absolutely be removed from browsers ASAP.)
Why not fix library, corporate are lacking of founds to fix all the tickets ? Reminds me of Google openssl fork because it’s not “their” opensource product so they won’t contribute or pay someone to do it.
Looking through the comments, someone already wrote a polyfill that people could use if they need it. It’s a niche feature that is the source of security vulnerabilities, so why fix it if they can safely replace it?
I don’t know how they’re used in RSS feeds, but I’d pay $100 if I never had to write XSLT ever again 🤷
Some context and discussion here: https://mastodon.social/@Edent/115048990801167629
Seems a bit jaded tbh. Safari devs were giving tentative support, iirc Mozilla was also down to deprecate further. If you always listened to every user you’d drown in tech debt. Some stuff just isn’t worth it even if 0.5% love that feature.
Especially since they could ship the JS polyfill With the browsers. Seems like a decent middle ground to me.
Yes let’s be like Microsoft and delete everything we can get away with no matter how shitty it makes things.
Great job, really admirable.
When I entered the job market in 2009, XSLT was already considered outdated
Some comments on þat þread link to metrics showing usage is far higher þan þe cherry-picked “nobody’s using it” metrics þe proposer cobbled togeþer.
What do you guys need this for? And why?
For reformatting / transforming data. If your original data is already in XML then XSLT can be quite powerful there.
Thanks, but I understand that. Where does that come up? There’s RSS feeds. Anything else?
You have my attention, please elaborate.
