News for hackers. Stuff that matters.
Re:XSLT RIP by rhdunn on Monday November 10, 2025 @04:06AM (#45874009)
libxslt != XSLT.

It's like removing JPEG support because libjpg is insecure!

Re:XSLT RIP by jeltz on Monday November 10, 2025 @04:20AM (#45874119)
Which would be a totally sensible thing you do. Especially if jpeg was a rarely used image format with few libraries supporting it, the main one being unmaintained.
Re:XSLT RIP by nflekkhnnn on Monday November 10, 2025 @11:42AM (#45877746)
Google is on a trajectory to replace jpeg with webp, haven’t you noticed?
Re:XSLT RIP by TingPing on Monday November 10, 2025 @04:46AM (#45874279)
If this were true you could fix this today with the other library. That library is the only implementation used and it’s features are relied upon.
Re:XSLT RIP by chrismorgan on Monday November 10, 2025 @06:43AM (#45874975)
Firefox doesn’t use libxslt. I presume IE didn’t either. It’s only WebKit-heritage browsers that use libxslt.
Re:XSLT RIP by TingPing on Monday November 10, 2025 @12:52PM (#45878604)
TIL about Firefox. They have their own in-tree solution. Very interesting but not trivial to use for external projects.