But also, be Mozilla: decimate your own plugin ecosystem, kill half of plugins, force to rewrite the other 50%. But a few years later support this 1 extension, and people will remember that you're a good guy.
When they've adoped Chrome plugins, they've effectively gave up their shares of relevance to Chrome and now they're paying for it.
The 'newer' Manifest V3 replaced the V2 webRequest API with a more limited declarativeNetRequest API.
The original allowed the intercept and blocking of network requests in real-time as generated, the replacement allows a limited subset of filter blocking after requests have been sent and returned.
ie: V2 allowed for less network traffic and greater amount of filtering, V3 provides slower page completes and limited filtering.
And we have adblockers built-in in various browsers now.
So since we have built-in adblockers, we don't really need MV2 functionality anymore? Why oppose MV3?
I mean why people want to oppose MV3 instead of simply asking your favorite browser to expose the browser-specific API for missing functionality, like it was done "in the old days"?
If Google wants to block MV3, then let it block it, and ask browsers to expose missing API. Of course this won't happen in Chrome, but back in my days when software was limited, we simply stopped using it in favor of more complete software.
If you're more enlightened, then the best you can do is to explain it to lesser beings, not virtue signal that you know better but others are unworthy of your knowledge.