Also less development overhead, when one does not need to develop for Chrome any longer. Seems like a sweet deal to take. With a more focused development, we might see more improvements for the code of the Firefox extension.

To expand on your comment a little: The new API means uBlock Origin cannot do useful things that it does now. gorhill/Raymond is not refusing to implement a new API, he is refusing to nerf uBlock Origin.

That's a stance I like very much. And it is good news for Firefox for sure, since the roughly 30% (last I checked) of users that use privacy-enhancing extensions are being handed a very good incentive to switch.

Thanks. uBlock Origin has a unique author who does not bend with "acceptable ads" nonsense and it's a shame to lose that addon. Hopefully something similar will emerge. I think that Chrome developers have a good reason to abandon old API, because Apple did something similar with Safari approach to ad blocking. Also it's a good thing if more users will migrate from Chrome. While I, myself, use it and love it, I think that healthy competition benefits everyone.

Unless you're on AD:

> The blocking version of the Web Request API remains available for managed extensions because of the deep integrations that enterprises may have between their software suites and Chrome.

Guess that leaves corporate Mac and Linux users in the lurch.