|
|
|
|
|
by ravenstine
1720 days ago
|
|
Are these changes actually needed, though? As much as it makes sense to use service workers, for instance, this seems like a rationalization to shoehorn in Google's anti-features. It's not like background webpages are broken or even hard to use. It's not like everyone's clamoring for their ad blockers to use less resource or for Chrome to be faster. There was a time when I switched to Chrome because I believed it to be superior. Now that I find the extensions I use to be nearly as important as the browser itself, I can't imagine why ad-hating privacy-focused individuals would punish themselves by using Chrome. Firefox has a few performance quirks in contrast to Chrome, but overall it's in a state where it competes in most cases. As much as I can complain about Mozilla's organizational issues, I can be far more assured that they aren't going to cause my extensions to become nerfed for A Good Reason (TM). |
|
> It's not like everyone's clamoring for their ad blockers to use less resource or for Chrome to be faster.
some people do: https://news.ycombinator.com/item?id=28672377 - "Brave reduces the page load performance cost of its adblocker"
original article having some impressive improvement numbers.