ads
ads
As always, it's probably a little from column A and a little from column B, but mostly column A with the "unfortunate" side effect of column B. Google has had years to remove ad blockers from the extension marketplace, for example, and they'd need to write a lot less code relative to MV3.
Not building uBlock Origin into Chrome was the mistake they made here. Once there is a known-good ad-blocker built in, nobody cares about extensions anymore. (Except for the steal-your-data extensions, whose authors are definitely amongst us on HN.)
It might also solve issues with security, but Google's complete refusal to work with the community to find common ground shows what they're really after.
You make this sound easy. It isn't.
Manifest V3 doesn't stop this.
Also, Google reviews every extension and update on the Chrome Web Store. The API is irrelevant when Google is asleep at the wheel.
Absolutely not true. No one has the manpower to actually review/understand all the code that is being pushed to the store. Extensions are automatically approved after a few minutes.
Mozilla tries but it's more of a spot check after the extension is being published.
This is not true in my experience. In fact I've experienced reviews lasting days or weeks with the Chrome Web Store.
I think GPs point stands - whether or not they actually review every update, they make the claim that extensions are reviewed, and they're reviewed often enough that they should be able to catch genuinely dangerous extensions.
Most users are not like this. They really do benefit from a restricted experience. That's why app store and extension restrictions should exist.
The problem is when engineers go all in on the restrictions, and completely abandon the other set of users. This is software, it can have an infinite number of knobs and customisations. It's not a table, which can only have a fixed number of legs.