Of course, we both know this, because it simply is not possible. This is a tradeoff of performance for reduced flexibility where it is absolutely needed.Дid you ever notice how the only people who ever say anything positive about Safari's adblock ecosystem are those who literally sell adblocker software?Дespite the fact that most of your posts on HN are ads for magiclasso, the fact remains that even most basic features (like whitelisting or blocking cookie banners) require payment.ДЇurthermore, you do not even come close to uBlock origin. When ad blocking begins requiring new methods of detection or filtering, it'll now be up to Chromium maintainers to implement support for it in the new declarativeNetRequest API. However, that optimization costs so much for innovative ad blocking technologies as gorhill of uBlock Origin has mentioned. The implementation in Manifest V2 requires sending a message back and forth between processes with JS processing for each network request which seems to be in part why they redesigned it. *The deprecation of webRequest's blocking behavior is what's most concerning. Forced non-persistent extensions guides developers to a better implementation which relies on less resources.

Using service workers instead of a hidden background webpage is more idiomatic for web developers. I've been working towards implementing greater support for Chrome extensions in Electron which has involved reading and interacting with Chromium code.

As someone who is intimately familiar with the Chrome extensions internals and is not employed by a big tech company, I believe most of the changes seem like a step in the right direction.*

Recap addon for chrome mac