Hacker News Reader

Comment by layer8 | Hacker News Reader

One reason Google wants to remove V2 support is to make implementation changes that V2 currently prevents. This means that a Chromium fork that preserves V2 support will likely have to diverge further and further from Chromium over time (or rather, Chromium will diverge).

View on HN

which hopefully means Brave and friends will switch to being based on Firefox instead. Could lead to some positives.

Alternatively it could be that all alt browser companies will maintain one chromium fork that preserves manifest v2. Or V3 but with a lot more rules.

Brave isn't affected by this anyway, brave shields don't depend on the extension API.

Also Gecko is just a factually worse engine, that's why they didn't use it.

Gecko is not worse, though it used to be worse before Electrolysis landed. It's just that Mozilla Corp is mostly kept alive by Google so might as well remove the indirection and go straight to the browser that Google maintains

How much money do you reckon it costs for just the Firefox browser? I know Mozilla waste a lot of effort on projects like Firefox OS, the Firefox mobile, politics, etc. But the actual browser it's self and it's hosting?

I just wonder if they end up dropping Manifest V2, if a patron model would work to maintain a fork properly...

Those projects exist because they are within the scope of Mozilla Foundation, which is wider than just building a browser.

It's faster, supports more features and is more secure, especially on Linux [1].

1. https://madaidans-insecurities.github.io/firefox-chromium.ht...

I did some searching but I couldn't find information about this. Can you share where you read it?

[citation needed]

I've heard this said a few times but no one has ever supplied any reputable source other than fanciful speculation. It's become such a meme at this point that I'm pretty sure it's just harmful disinformation.

Maybe I succumbed to that meme, I honestly don’t remember. I’m not in favor of what Google is doing. But I’m sure the implementation divergence will happen if V2 support is dropped. It pretty much always does once a public API is removed.

Reply on news.ycombinator.com