>Remember, you are a web developer, not a chrome platform developer. Don’t be complicit in Google’s slow-moving coup.
This reflects a fundamental misunderstanding, much like how many think standards groups (e.g. W3C) decide how the browsers works.
(Standards groups can invent the best feature ever for the Web ... and it won't matter in the slightest if browser makers don't adopt it. ALL STANDARDS ARE SET BY BROWSER MAKERS ... the standards bodies are just the mechanism they use to do it.)
Likewise, the browser a web developer user uses is already set for them. EVERY web dev (except those at companies big enough to care about the "long tail" of browsers) uses one browser: the most popular one.
It has nothing to do with politics or being complicit, and everything to do with "You have a job to do, why would you make it take twice as long by testing everything with an unpopular browser, when 99 out of 100 times that testing will find nothing and be a total waste of your time?"
> This reflects a fundamental misunderstanding
No, it doesn't. I wasn't talking about web standards bodies. I'm talking about the practical reality of the web as a platform that is resilient against slight differences between browsers. Such resilience can only come from developers who understand that their job is to target the web and not just Chrome.
It is you who misunderstands:
> It has nothing to do with politics or being complicit, and everything to do with "You have a job to do, why would you make it take twice as long by testing everything with an unpopular browser, when 99 out of 100 times that testing will find nothing and be a total waste of your time?"
You are literally arguing for the web to become the Chrome Platform for the convenience of web developers. Sure we can have other browsers, so long as they're perfectly compatible with Chrome's quirks. This is precisely what it means for the web to be the Chrome Platform, not the open web. We've already reached the point where it's assumed that Chrome is perfect and anything that deviates from Chrome is someone else's bug. It's sad.