Chrome Canary just killed uBlock Origin and other Manifest V2 extensions androidpolice.com 26 points by abixb 3 hours ago
Arnt an hour ago I have heard that the real underlying problem concerned resource usage (ten thousand regexp matches etc). But only now do I wonder why the browser's reaction is to remove an API instead of to limit the amount of CPU extensions can use. grobbyy 3 minutes ago The browsing experience is dramatically faster with uBlock. The thousands of regexps don't come close to the CPU or memory load of ads.A 386 could handle a regexp fine. Compare that to audio or video decoding for ads. Not the same ballpark by orders of magnitude.It's dead because Google makes money from ads. I shifted to Firefox ages ago.
grobbyy 3 minutes ago The browsing experience is dramatically faster with uBlock. The thousands of regexps don't come close to the CPU or memory load of ads.A 386 could handle a regexp fine. Compare that to audio or video decoding for ads. Not the same ballpark by orders of magnitude.It's dead because Google makes money from ads. I shifted to Firefox ages ago.
mrkramer 27 minutes ago That's good, at least more and more people will move away from Chrome. beardyw a minute ago In terms of HN probably. In terms of all users, probably very few
I have heard that the real underlying problem concerned resource usage (ten thousand regexp matches etc). But only now do I wonder why the browser's reaction is to remove an API instead of to limit the amount of CPU extensions can use.
The browsing experience is dramatically faster with uBlock. The thousands of regexps don't come close to the CPU or memory load of ads.
A 386 could handle a regexp fine. Compare that to audio or video decoding for ads. Not the same ballpark by orders of magnitude.
It's dead because Google makes money from ads. I shifted to Firefox ages ago.
That's good, at least more and more people will move away from Chrome.
In terms of HN probably. In terms of all users, probably very few