Bypassing Google's big anti-adblock update

Even if bigs exists to work around what Google is doing, that isn’t the right way forward. If people don’t agree with Google move, the only correct course of action is to ditch Chrome (and all Chromium browsers). Hit them where it hurts and take away their monopoly over the future direction of the web.

A monopoly achieved thanks to everyone that forgot about IE lesson, and instead of learning Web standards, rather ships Chrome alongside their application.

> instead of learning Web standards, rather ships Chrome alongside their application

I am confused.

- The "shipping Chrome alongside their application" part seems to refer to Electron; but Electron is hardly guilty of what is described in the article.

- The "learning web standards" bit seems to impune web developers; but how are they guilty of the Chrome monopoly? If anything, they are guilty of shipping react apps instead of learning web standards; but react apps work equally well (or poorly) in all major browsers.

- Finally, how is Chrome incompatible with web standards? It is one of the best implementer of them.

Devs, particularly those with pressure to ship or who don't know better, unfortunately see 'it works in Chrome' as 'it works', even if it is a quirk of Chrome that causes it to work, or if they use Chrome related hacks that break compatibility with other browsers to get it to work in Chrome.

- Sometimes the standards don't define some exact behavior and it is left for the browser implementer to come up with. Chrome implements it one way and other browsers implement it the other way. Both are compatible with the standards.

- Sometimes the app contains errors, but certain permissive behaviors of Chrome mean it works ok and the app is shipped. The developers work around the guesses that Chrome makes and cobble the app together. (there may be a load of warnings in the console). Other browsers don't make the same guesses so the app is shipped in a state that it will only work on Chrome.

- Sometimes Chrome (or mobile Safari) specific APIs or functions are used as people don't know any better.

- Some security / WAF / anti-bot software relies on Chrome specific JavaScript quirks (that there may be no standards for) and thinks that the user using Firefox or another browser that isn't Chrome or iOS safari is a bot and blocks them.

In many ways, Chrome is the new IE, through no fault of Google or the authors of other browsers.

Before shipping any web site/app, make sure it works in Apple Safari Mobile is usually the one that is dragging it is foot in Web Standards.

On the contrary, they are the last one standing fighting Google takeover of the Web as ChromeOS development platform.

Without Safari we are done, just close shop on the Web standards group.

This is a lesson in capitalism. It’s so much more profitable to ignore small users bases when you can just tell them to “try switching to Chrome”.

I think you’re wrong about Safari itself being the reason chrome isn’t a 90%+ market owner; rather, it’s apple’s requirement that no other browser engine can exist on iOS.

> I think you’re wrong about Safari itself being the reason chrome isn’t a 90%+ market owner; rather, it’s apple’s requirement that no other browser engine can exist on iOS.

It sounds like capitalism has so far saved us from a Chrome monopoly, then.

Capitalism doesn't exist. The fact that trademark, copyright, and patents exist nullify capitalism.

There can be no free market if your government intervenes in every transaction.