Live data from Hacker News

Chrome is looking to permanently drop MV2 extension

neowin.net

121–130 of 480 posts

Re: Chrome is looking to permanently drop MV2 extension

#121
post #54

Earlier quoted context omitted.

I'm a Firefox user for about 20yrs (since Firefox 3); but too often I have to use Chrome, as so many sites only work properly on it; Firefox is really buggy or laggy on those websites; For a time, all those AI chat web pages were just very slow on Firefox even with very little context, whereas Chrome only gets laggy when there is a lot of context.

How many extensions do you use on laggy FF?

Not using many extensions on my case, but Google meet remains unusable for a long time, sound is horrible during meetings. Chrome on the other hand works fine

Re: Chrome is looking to permanently drop MV2 extension

#122
post #104

So, what's next? Will Chrome ship with hard coded DNS, so that DNS based adblockers will stop working as well? Where (and when) does my rights what to display on my devices end?

Ship has already sailed, it's called DoH. Please note, that it is to make your DNS safer and has absolutely nothing to do with removing your ability to resolve DNS in whatever way you want to(cough adblock cough).

I guess I just missed that?! I'm running a mix of Adguard and nextdns blockers on some of my mobile devices, and both are apparently handling the DoH issue for you; by just blanket blocking the resolvers and/or ports, to force a fallback.... I need a Beer.

Re: Chrome is looking to permanently drop MV2 extension

#123
post #4

Why are people on HN still using Chrome? (or Edge, or Opera…)

There are 2 reasons why I'm using chromium (with ublock origin lite) over Firefox:

1. Chromium is significantly faster (maybe 5 to 10x faster on certain tasks mostly around canvas but anything that requires fast ui really). Every time I use Firefox it feels like it has some kind of serious problem. If chrome was this slow I would stop working and start investigating what part of my computer is broken. This experience hasn't changed over span of 10 years, 3 OSes and several computers.

2. Neverending caching issues on Firefox. It just caches too aggressively which makes development really annoying to a point where anytime I encounter issue on Firefox my first thought is "Is this Firefox caching issue?". On chrome when I change button color and I don't see it, I know I made a mistake. If I change button color on Firefox, my first thought is, is this Firefox caching issue? When I develop web I have very quick update loop and I really can't be questioning browser. I cannot work like this. Firefox is unusable for me.

Re: Chrome is looking to permanently drop MV2 extension

#125
post #119
post #10

I wonder what will Vivaldi do. They say that their built-in content blocker is "good enough" that you supposedly don't need uBO (I very much disagree) but they also keep MV2 extensions working to this day.

They can only support MV2 extensions as long as Google continues to maintain them. Their tech stack is heavily JavaScript-focused, as their entire UI is written in JavaScript.

How is it half of HN is convinced Firefox can compete with Chrome in its entirety and the other half is convinced nobody can possibly maintain a single additional API version on Chromium?

Re: Chrome is looking to permanently drop MV2 extension

#126

Earlier quoted context omitted.

Firefox haven't caved in so far. Why do u think it might in future?

> Firefox haven't caved in so far. Why do u think it might in future? Because pretty much all their revenue comes from Google.

Making Firefox even less desirable by "googlifying" it pushes Firefox users away and kills its image of a viable competitor. That's exactly what Google is paying for.

Why would Google destroy the cover they have for keeping control over Chrome and 70% of internet users, just to squeeze a bit more ad revenue from what, 2% of users?

Re: Chrome is looking to permanently drop MV2 extension

#127

Look, we're having a good time on Firefox since November 9, 2004. Come join us!

Then again, our laptop battery only lasts 1/3 as much on MacOS.

I know, I know. The community keeps pretending this isn’t an issue for the last, hum, 15 years? But it is, and for people that are looking for a tool and not for a statement, it quickly drives them away from Firefox back to Chrome browsers.

Re: Chrome is looking to permanently drop MV2 extension

#128

Earlier quoted context omitted.

Because Mozilla, at least from the outside appears to have been horribly mismanaged for the past 20-25 years and only survived because the ad money kept rolling in. I'm not knocking Mozilla for taking money from Google, it was a smart move. Most users would use Google anyway, so Mozilla pocketing billions by making users preferred search engine the default didn't really hurt anyone. Some of that money should however…

> the ad money kept rolling in Why "ad money"? That's a very uncharitable interpretation and for anyone not aware of the situation it's misleading. They're not paid for ads or by ads, they're paid by Google to continue being a viable alternative to Chrome. Is every Google employee getting "ad money" every month, or a salary? The payment is more accurately described as a protection tax.

Technically yes

Re: Chrome is looking to permanently drop MV2 extension

#129

AdGuard MV3 works fine. Still switch to FF if you can, more diversity in the ecosystem benefits everyone.

wasn't mv3 a dumbed down version? So it "does not work just fine" as some ads slip through?

MV3 is actually a faster but less capable version.

With MV2, every request must be filtered with slow, JIT, garbage-collected JavaScript code. In MV3, filtering is handled by native browser code using the list provided by extensions. UserScripts could be used to modify the DOM, but that requires power users to manually enable it.

Post reply on HN