• kbin_space_program@kbin.run
    link
    fedilink
    arrow-up
    29
    arrow-down
    16
    ·
    edit-2
    6 months ago

    Mentions UBlock seems.to be fast and safe, but that the API used lets extensions look at everything you do amd can dramatically affect browser speed. Implying that UBlock Origin is responsible for Chrome being such a memory Hog and that they, not Google, are the ones after your data.

    • Deebster@programming.dev
      link
      fedilink
      English
      arrow-up
      29
      arrow-down
      1
      ·
      6 months ago

      That performance cost seems to be negligible in uBlock Origin and other popular ad blockers that have focused on optimization […], but there were probably other extensions not doing that well.

      The article goes out of its way to not do what you’re accusing it of. I don’t understand how you’ve managed to read the article as having the opposite slant as what it actually does.

    • corbin@infosec.pubOP
      link
      fedilink
      English
      arrow-up
      22
      arrow-down
      1
      ·
      6 months ago

      Except the part where it didn’t imply that at all?

      That performance cost seems to be negligible in uBlock Origin and other popular ad blockers that have focused on optimization (uBO has an explainer wiki page), but there were probably other extensions not doing that well. It’s not hard to see a situation where multiple poorly-optimized extensions installed using the Web Request API could dramatically slow down Chrome, and the user would have no way of knowing the issue.