this post was submitted on 29 Mar 2026
358 points (97.9% liked)

Technology

83966 readers
4728 users here now

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


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related news or articles.
  3. Be excellent to each other!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
  9. Check for duplicates before posting, duplicates may be removed
  10. Accounts 7 days and younger will have their posts automatically removed.

Approved Bots


founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] Feyd@programming.dev 126 points 3 weeks ago (2 children)

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

[–] Kushan@lemmy.world 106 points 3 weeks ago (2 children)

I'm not entirely sure what the "maintenance burden" even is on a tech that hasn't changed in decades.

[–] floofloof@lemmy.ca 42 points 3 weeks ago* (last edited 3 weeks ago) (1 children)

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 reduce the surface area for attacks.

[–] 73QjabParc34Vebq@piefed.blahaj.zone 36 points 3 weeks ago (1 children)

Big tech has been straining the libxml2 dev who recently got annoyed with them. Instead of helping maintain the libraries they ship on billions of computers, Google is trying to reduce there use.

https://socket.dev/blog/libxml2-maintainer-ends-embargoed-vulnerability-reports

That was a good read. Very eye opening to the underpinning problems in the oss world, caused by the proprietary world. Really, we should all use a license that prohibits commercial uses of any oss code.

[–] cecilkorik@piefed.ca 17 points 3 weeks ago (1 children)

0.02% of page loads is honestly way more than I would've expected. The fact that they would look at that number and see an excuse to remove a feature like this is honestly a gigantic red flag for the way these browsers are being developed. Granted, it's not that surprising if you've been paying attention to the embrace-extend-extinguish march of web technologies towards a walled garden controlled by tech giants, but this is part of the writing on the wall, folks.

[–] 418_im_a_teapot@sh.itjust.works 2 points 3 weeks ago

RSS is enabled by default on every WordPress install. That's a big part of it.