Should we remove XSLT from the web platform?

a year ago by taaz to c/technology

What is the issue with the HTML Standard? XSLT v1.0, which all browsers adhere to, was standardized in 1999. In the meantime, XSLT has evolved to v2.0 and v3.0, adding features, and growing apart f...

cross-posted from: https://lemmy.bestiver.se/post/555312

Comments

My comment: It seems google is trying to pull another Manifest v3 and JPEGXL - propose then ignore everyone and do it anyway.

thfi 17 points a year ago

Some context and discussion here: https://mastodon.social/@Edent/115048990801167629

save

path: 0 18865210, hotness: undefined, score: 17, children: 5

mormund 6 points a year ago

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.

save

path: 0 18865210 18869455, hotness: undefined, score: 6, children: 4

amju_wolf 3 points a year ago

Especially since they could ship the JS polyfill With the browsers. Seems like a decent middle ground to me.

save

path: 0 18865210 18869455 18876564, hotness: undefined, score: 3, children: 0

Guidy -1 points a year ago

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.

save

path: 0 18865210 18869455 18869672, hotness: undefined, score: -1, children: 1

iopq 1 point a year ago

When I entered the job market in 2009, XSLT was already considered outdated

save

path: 0 18865210 18869455 18869672 18881219, hotness: undefined, score: 1, children: 0

Sxan -5 points a year ago

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.

save

path: 0 18865210 18869455 18872187, hotness: undefined, score: -5, children: 0

coreray00 10 points a year ago

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 🤷

save

path: 0 18874151, hotness: undefined, score: 10, children: 0

cypherpunks 5 points a year ago

some context.

(tldr: libxslt is a significant source of vulnerabilities and it should absolutely be removed from browsers ASAP.)

save

path: 0 18880785, hotness: undefined, score: 5, children: 0

General_Effort 3 points a year ago

What do you guys need this for? And why?

save

path: 0 18873532, hotness: undefined, score: 3, children: 4

Zwuzelmaus 8 points a year ago

For reformatting / transforming data. If your original data is already in XML then XSLT can be quite powerful there.

save

path: 0 18873532 18874815, hotness: undefined, score: 8, children: 3

isVeryLoud 2 points a year ago

You have my attention, please elaborate.

save

path: 0 18873532 18874815 18878570, hotness: undefined, score: 2, children: 1

Zwuzelmaus 3 points a year ago

https://en.m.wikipedia.org/wiki/XSLT

save

path: 0 18873532 18874815 18878570 18880456, hotness: undefined, score: 3, children: 0

General_Effort 1 point a year ago

Thanks, but I understand that. Where does that come up? There's RSS feeds. Anything else?

save

path: 0 18873532 18874815 18887081, hotness: undefined, score: 1, children: 0

vane 3 points a year ago

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.

save

path: 0 18880974, hotness: undefined, score: 3, children: 3

sugar_in_your_tea 1 point a year ago

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?

save

path: 0 18880974 18881689, hotness: undefined, score: 1, children: 2

vane 2 points a year ago

To have good XSLT library that follows standard ? But no we got html5 and now web components and shadow DOM slop that is not even accessible from javascript instead of proper XSLT because nobody wants to deal with it. XPath is broken since the beginning of this shit show.

save

path: 0 18880974 18881689 18895998, hotness: undefined, score: 2, children: 1

sugar_in_your_tea 1 point a year ago

It sounds like you're complaining about not having consistent DOM state, not about the XSLT library. Whether the library is built in to the browser or an add-on is irrelevant to your problem.

save

path: 0 18880974 18881689 18895998 18898447, hotness: undefined, score: 1, children: 0

zod000 1 point a year ago

No, we shouldn't remove it ffs.

save

path: 0 18898851, hotness: undefined, score: 1, children: 0

This is a most excellent place for technology news and articles.

Our Rules

Approved Bots

This is a most excellent place for technology news and articles.

Our Rules

Approved Bots