Nah, there's plenty of examples of sites breaking on Firefox. For example, the recent degraded performance on Youtube linked to Firefox User Agent strings.
Do people honestly believe that if they keep recommending FF, people will magically switch to FF and Google will be forced to stop its anti-competitive practices?
Because holding that against Firefox is exactly what Google is counting on. And the more you recommend it the harder it is for Google to continue its anti-competitive practices.
The more you fall a fool for Google's (or Microsoft a decade ago) practices, the worse the experience for everyone is in the future.
Anyways, there's simple extensions that will sidestep Chrome's bs. In addition, you'll soon to be able to get an adblocked experience that you can only get on Firefox. That means less network traffic, faster loading websites, and better user privacy
Before that they had a popup that would timeout after 15s (?). At that point I tried disabling uBlock on Youtube but found the ads stacked up to much longer, so the 15s delay was more acceptable.
As expected, this will probably continue to be a cat and mouse game.
Do you honestly believe that it's OK for Google to just keep being anti-competitive? Or that this is a completely inevitable and unfixable state of affairs?
We can, should, and will hold Google accountable for its monopolistic conduct, and this is absolutely part of that.
My move back to FF has been slow (as mentioned already too) but I've been recommending it to others, who don't have my self-inflicted blocker, for some time. Maybe some will stop listening if I keep mentioning it, but people online I'll never meet in person are hardly a great loss in my life. The sort of people who are going to take such issue in RealLife™ are likely those just paying me attention in exchange largely for free tech support (the matter isn't likely to come up in other contexts) and they can do one anyway too.
Both of those will seriously hamper a more advanced adblock like UBlock Origin
The limits are 30,000 static rules and 30,000 dynamic rules. Running tens of thousands of regexs for each request can lead to a performance impact. Allowing for even higher limits may result in people having a worse experience from the browser becoming slower. The API was designed such that these limits can be increased in the future as available computation and user needs change over time. Getting extension developers to design their extensions in a way where they have to think about not slowing down the browser too much I think is a good thing and I would not call these current limits severe.
>also prevents plugins from updating block lists themselves
declarativeNetRequest lets rules be added and removed dynamically by the extension.
>forces those updated lists to go through the plugin store
The Chrome team has said that configuration can be updated outside of a store update. What the Chrome web store does not want are extensions that download and run code. This policy does not related to mv3.
If no engineering time was spent on Firefox, and it’s broken in Firefox, that’s a Firefox problem.
If active engineering time was spent on _deliberately breaking_ Firefox, then yes, I don’t think that’s a Firefox problem. I think it’s a website problem at that point.
im curious to see what effect ublock not working as well on chrome as it will on firefox will have to the demographics, if there's no shift then that's a hurdle that has to be overcome by either firefox by some sort of engineering, google, or via legislation
Besides specific Google products, most everything works across all 3 major engines.
In addition, Mozilla adds specific code to Firefox to counteract anti-competitive practices on specific websites
Unless you use Edge on Windows you still have the same limitation (or the windows store Netflix app).
It is unfortunate that Firefox doesn’t do more to help us avoid sites programmed by devs who are too incompetent to follow standards, really.