I found this post highly editorialized. Here's the actual response if you want to understand the context, instead of simply seeing bits and pieces with a journalist's spin. https://groups.google.com/a/chromium.org/forum/#!topic/chrom... Also, the headline seems mostly incorrect. The gist of it, as I understand, is that Chrome is enforcing a migration from the webRequest API to a new declarativeNetRequest API. The lat…
I really think it is a bad practice to force adoption of a new API that can't fulfill the same functions as the previous one.
Nobody would be here talking about this if they just made the new API without breaking add blocking (useful add blocking), and then forced people to move.
Even more so given that it looks really bad when your main goal is to serve people ads.