Technology

59339 readers

5228 users here now

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

Our Rules

Follow the lemmy.world rules.
Only tech related content.
Be excellent to each another!
Mod approved content bots can post up to 10 articles per day.
Threads asking for personal tech support may be deleted.
Politics threads may be removed.
No memes allowed as posts, OK to post as comments.
Only approved bots from the list below, to ask if your bot can be added please contact us.
Check for duplicates before posting, duplicates may be removed

Approved Bots

founded 1 year ago

MODERATORS

[email protected]

288

Here's what's happening to ad blockers in Google Chrome (and other browsers) (www.spacebar.news)

submitted 5 months ago by [email protected] to c/[email protected]

90 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 13 points 5 months ago* (last edited 5 months ago) (2 children)

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.

[–] [email protected] 28 points 5 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.

[–] [email protected] 21 points 5 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.