The new way has the extension give a list of patterns to block to chrome, and from there it will block any request that matches.
The stated reason is that this is for privacy, to prevent extensions from being able to gather data about every request a browser makes. Currently, a malicious extension could send every url a user visits to some central collection server. The new way prevents that.
Is the trade off worth it? I personally think no, but I do think many people don't realize that as blockers have the capability to collect every url you visit if they wanted.
They're not lying. This was listed as one of the reasons by Google.
>The declarativeNetRequest API provides better privacy to users because extensions can't actually read the network requests made on the user's behalf.
https://developer.chrome.com/extensions/declarativeNetReques...
Seems like a pretty major change to me.