Chrome is right to remove the webRequest extension API(ctrl.blog)

14 pointsby woodrow7 jaar geleden0 comments

Chrome is right to remove the webRequest extension API

https://www.ctrl.blog/entry/removing-webrequest-api.html

3 comments

benatkin7 jaar geleden

This is a straw man for clickbait. The articles the headline is responding to aren't complaining about the features of the new API, but about the removal of important plugin functionality. The new features are a red herring. A declarative API could co-exist just fine with an API that supports adding a hook.

I thought of flagging this but it's late and I'm not sure it's warranted and I'm gonna let the rest of HN figure out what to do.

jonnytran7 jaar geleden

> I’m absolutely certain that Chrome would have preferred fixing the API if that was at all possible rather than replacing it with a new one.

This is such bullshit. Even if this were true, they could have replaced it with an API that didn't cripple ad blockers. Or they could have simply added an alternative API that could be used in certain cases _without_ deprecating the webRequest API.

chris_wot7 jaar geleden

For a previous conversation see https://news.ycombinator.com/item?id=20044430