Adios Google that once was. Ad blocking does cause performance issues, but revenue ones.
Google backtracks on Chrome modifications that would have crippled ad blockers
21–30 of 169 posts
Re: Google backtracks on Chrome modifications that would have crippled ad blockers
#22>> Google changes stance on upcoming Chrome Manifest V3 changes as benchmark shows they lied about performance hit.....Hours after the Ghostery team published its study and benchmark results, the Chrome team backtracked on their planned modifications. Adios Google that once was. Ad blocking does cause performance issues, but revenue ones.
Re: Google backtracks on Chrome modifications that would have crippled ad blockers
#23Duh, everyone knew that this was a non-issue. Now prepare for every other comment to be about how you should still be using Firefox.
Re: Google backtracks on Chrome modifications that would have crippled ad blockers
#24>> Google changes stance on upcoming Chrome Manifest V3 changes as benchmark shows they lied about performance hit.....Hours after the Ghostery team published its study and benchmark results, the Chrome team backtracked on their planned modifications. Adios Google that once was. Ad blocking does cause performance issues, but revenue ones.
I wouldn't really trust the Ghostery team either. They don't exactly have the best track record.
Re: Google backtracks on Chrome modifications that would have crippled ad blockers
#25> "Another clarification is that the webRequest API is not going to be fully removed as part of Manifest V3," said Chrome engineer Devlin Cronin [emphasis his].
But the full quote shows what he's talking about:
> Another clarification is that the webRequest API is not going to be fully removed as part of Manifest V3. In particular, there are currently no planned changes to the observational capabilities of webRequest (i.e., anything that does not modify the request). We are also continually listening to and evaluating the feedback we’re receiving, and we are still narrowing down proposed changes to the webRequest API.
The only commitment is to not modify the read-only "observational capabilities".
Re: Google backtracks on Chrome modifications that would have crippled ad blockers
#26Re: Google backtracks on Chrome modifications that would have crippled ad blockers
#27Things like this is why it is so important for the web to have multiple browsers available to choose from.
Saying we need multiple browsers, then using chrome or its clone actually makes the situation worse.
Also chrome is no longer snappy as it was initially.
Re: Google backtracks on Chrome modifications that would have crippled ad blockers
#28Things like this is why it is so important for the web to have multiple browsers available to choose from.
Re: Google backtracks on Chrome modifications that would have crippled ad blockers
#29Things like this is why it is so important for the web to have multiple browsers available to choose from.
And that's why this announcement should make people switch to alternatives with different engine like FF. Saying we need multiple browsers, then using chrome or its clone actually makes the situation worse. Also chrome is no longer snappy as it was initially.