Should we remove XSLT from the web platform?

Comments

• thfi@discuss.tchncs.de ⁨6⁩ ⁨days⁩ ago

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

  source

  • mormund@feddit.org ⁨6⁩ ⁨days⁩ 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.

    source

    • Guidy@lemmy.world ⁨6⁩ ⁨days⁩ 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.

      source

      • -> View More Comments
    • Sxan@piefed.zip ⁨6⁩ ⁨days⁩ 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.

      source
    • amju_wolf@pawb.social ⁨6⁩ ⁨days⁩ ago

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

      source
• coreray00@discuss.online ⁨6⁩ ⁨days⁩ 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 🤷

  source
• cypherpunks@lemmy.ml ⁨5⁩ ⁨days⁩ ago

  some context.

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

  source
• vane@lemmy.world ⁨5⁩ ⁨days⁩ 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.

  source

  • sugar_in_your_tea@sh.itjust.works ⁨5⁩ ⁨days⁩ 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?

    source

    • vane@lemmy.world ⁨5⁩ ⁨days⁩ 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.

      source

      • -> View More Comments
• zod000@lemmy.dbzer0.com ⁨4⁩ ⁨days⁩ ago

  No, we shouldn’t remove it ffs.

  source
• General_Effort@lemmy.world ⁨6⁩ ⁨days⁩ ago

  What do you guys need this for? And why?

  source

  • Zwuzelmaus@feddit.org ⁨6⁩ ⁨days⁩ ago

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

    source

    • isVeryLoud@lemmy.ca ⁨5⁩ ⁨days⁩ ago

      You have my attention, please elaborate.

      source

      • -> View More Comments
    • General_Effort@lemmy.world ⁨5⁩ ⁨days⁩ ago

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

      source