• Feyd@programming.dev
    link
    fedilink
    English
    arrow-up
    98
    arrow-down
    2
    ·
    5 months ago

    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
      link
      fedilink
      English
      arrow-up
      84
      ·
      5 months ago

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

      • floofloof@lemmy.ca
        link
        fedilink
        English
        arrow-up
        33
        arrow-down
        1
        ·
        edit-2
        5 months ago

        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.

  • Pirate2377@lemmy.zip
    link
    fedilink
    English
    arrow-up
    24
    ·
    5 months ago

    Wait, browsers still had RSS support? I thought that was deprecated a decade ago. I’ve been using dedicated apps for them

  • MinnesotaGoddam@lemmy.world
    link
    fedilink
    English
    arrow-up
    15
    ·
    edit-2
    5 months ago

    i browsed the web via RSS for a while. Maybe it’s time to get back to that. at least for some food blogs or something. anyone got a good rss reader?

  • Clent@lemmy.dbzer0.com
    link
    fedilink
    English
    arrow-up
    16
    arrow-down
    1
    ·
    5 months ago

    There are libraries that can polyfill this with almost zero effort. List should not effect any active site that offers rss feeds.

    • Feyd@programming.dev
      link
      fedilink
      English
      arrow-up
      1
      ·
      5 months ago

      It’s not zero effort at all. For XML(which RSS is) with xlst it is serving only 2 static files. The XML file with a reference to the xlst file, and the xlst file.

      The XML can be read without transformation by tools like RSS readers, but displayed with transformation into HTML for viewing in a browser with the xlst.

      You’re saying it is easy to polyfill, but involving JavaScript at all completely breaks the (useful) paradigm

  • JensSpahnpasta@feddit.org
    link
    fedilink
    English
    arrow-up
    13
    ·
    5 months ago

    It’s sad to see how browser manufacturers have been treating RSS for a while. Back in the day your Firefox would show you that a page has an RSS feed. You were able to click on it, see what was in there in human readable, not cryptic-XML style format, and you were able to subscribe to it. Then you had a nice little bookmark showing you everything this page had posted recently. RSS is a great technology and it really really sucks how Big Tech has tried to kill it.

  • vortexal@sopuli.xyz
    link
    fedilink
    English
    arrow-up
    5
    ·
    5 months ago

    I’m a little confused about this. While I’ve been using RSS feeds for several years, my only experience with RSS feeds is with Inoreader. Will this cause issues with the way that I’ve been using RSS feeds or will I be unaffected?