"The blocking ability of the webRequest
API is still deprecated, and Google Chrome's limited matching algorithm will be the only one possible, and with limits dictated by Google employees," wrote Hill
"It's annoying that they keep saying "the webRequest API is not deprecated"
as if developers have been worried about this -- and as if they want to drown the real issue in a fabricated one nobody made."
In his view, sluggish web page loading is due to Chrome "bloat" rather than the performance of the API itself for "well crafted extensions".
Hill also argues that to improve performance, Google should just follow Mozilla's approach in its Firefox browser.
"If performance concerns due to the blocking nature of the webRequest
API was their real motive, they would just adopt Firefox's approach and give the ability to return a Promise on just the three methods which can be used in a blocking manner."