[JeremyNT]

> This reads like FUD to me. The dev team know how important extensions are to their users.

Just because they know how important it is doesn't mean they care.

I'm sure Google also knew how important ad blocking was to many Chrome users when they decided to remove that functionality from their browser, too.

[BiosElement]

uBlock seems to work just fine, not sure why you're claiming they removed it.

[wtallis]

He's not claiming that they removed it. He's referring to the fact that Google announced their intention to remove the APIs that uBlock relies on. They haven't followed through with the plan yet, but neither have they completely backtracked. See eg. https://www.androidpolice.com/2019/05/29/google-still-plans-... and reports that they'll continue to provide that functionality only to enterprise users: https://9to5google.com/2019/05/29/chrome-ad-blocking-enterpr...

[techntoke]

Chrome devs made it clear that just because the API is changing that adblocking will still be supported and it will be faster. Sometimes APIs change.

[krageon]

The API was crippled, not changed. There is a fairly lengthy explanation of how it is bad and why by the author of uBlock Origin: https://github.com/uBlockOrigin/uBlock-issues/issues/338#iss...

[sascha_sl]

being able to decide for every request with code vs a limited number of patterns you can pre-populate is not an equally useful API replacement

[icebraining]

Chrome didn't remove ad-blocking.