Opinion: Chrome is Turning Into the New Internet Explorer 6 (theverge.com)

Tom Warren, writing for The Verge: Chrome now has the type of dominance that Internet Explorer once did, and we're starting to see Google's own apps diverge from supporting web standards much in the same way Microsoft did a decade and a half ago. Whether you blame Google or the often slow moving World Wide Web Consortium (W3C), the results have been particularly evident throughout 2017. Google has been at the center of a lot of "works best with Chrome" messages we're starting to see appear on the web. Google Meet, Allo, YouTube TV, Google Earth, and YouTube Studio Beta all block Windows 10's default browser, Microsoft Edge, from accessing them and they all point users to download Chrome instead. Some also block Firefox with messages to download Chrome. Hangouts, Inbox, and AdWords 3 were all in the same boat when they first debuted.

It's led to one developer at Microsoft to describe Google's behavior as a strategic pattern. "When the largest web company in the world blocks out competitors, it smells less like an accident and more like strategy," said a Microsoft developer in a now-deleted tweet. Google also controls the most popular site in the world, and it regularly uses it to push Chrome. If you visit Google.com in a non-Chrome browser you're prompted up to three times if you'd like to download Chrome. Google has also even extended that prompt to take over the entire page at times to really push Chrome in certain regions. Microsoft has been using similar tactics to convince Windows 10 users to stick with Edge. The troubling part for anyone who's invested in an open web is that Google is starting to ignore a principle it championed by making its own services Chrome-only -- even if it's only initially.

Comments

Monopolies gonna monopolize.

[Kenja]

Chrome is Googles gateway drug, of course they're going to try and get you to use it, and then start getting you to use all other things Google.

Re:Monopolies gonna monopolize.

[Z00L00K]

I don't see a problem when it comes to beta sites, but for full production the site has to be W3C compliant, just use the HTML and CSS validators to ensure that the site follows all standards. But when it comes to JavaScript then it's a headache of its own, primarily on Microsoft browsers where those browsers have a tendency to do things differently.

But a site that depends on JavaScript is in general a pretty crappy site.

Re:Monopolies gonna monopolize.

[amicusNYCL]

But when it comes to JavaScript then it's a headache of its own, primarily on Microsoft browsers where those browsers have a tendency to do things differently.

But a site that depends on JavaScript is in general a pretty crappy site.

That's pretty old-fashioned thinking. Today Edge is fast and holds to standards pretty well, while all of the most used and useful sites use a lot of Javascript. I wouldn't call any map site a "pretty crappy site" just because you have to have Javascript turned on to pan and zoom the map. That's the core functionality of the thing, trying to do some crappy workaround with arrows on each edge of the map where you click an arrow and the entire page refreshes with the map moved that direction is a stupid way to avoid Javascript.

It doesn't help

[rsilvergun]

that Firefox 57 just broke a mountain of plugins (mine included) and makes fixing said plugins difficult if not impossible (still wrestling with that).

Re:Microsoft

[MightyMartian]

Not to mention the fact that Microsoft continually finds new ways to harass or trick me into using Edge. Microsoft is in no position to complain.

Aww.

[msauve]

""When the largest web company in the world blocks out competitors, it smells less like an accident and more like strategy," said a Microsoft developer"

As they say - What goes around, comes around.

FUD

[sjbe]

It's also been horribly unstable for me since the 57 update. Not a crash for years before. Practically a daily occurrence when 57 first came out.

Works fine for me. Hasn't crashed once yet on me (and hasn't in years before that) and it's considerably faster than previous versions. I've run it on Windows, Macs and Linux on somewhere north of 20 machines. Color me dubious.

So far, Firefox 57 is somewhere around Windows 10 on the scale of new versions I don't want anywhere near my machines, but given security risks, staying on an older version is not practical in the long term.

Vague and unsupported assertions of instability from an Anonymous Coward. Very believable.

It might happen, but it's a big stretch right now.

[Anonymous Coward]

I was a web developer in the IE6 days. We're nowhere near where we were then. A few Google specific sites blocking Edge is hardly the horribleness that was IE6. With IE6, many, many, many companies thought of it as a software platform to develop software on. You also essentially HAD to have workarounds for IE6 because it didn't support standards.

I'm not in love with Google, and they can most certainly do wrong. But we aren't anywhere near what IE6 was, and I don't see the same thing happening with Chrome.

Also, Google's business model isn't the same as MS's. MS sees the web as a threat to its business model. The web IS Google's business model. They don't really have a huge interest in you using Chrome, they just want the web to grow in popularity. If other browsers adopt the same web standards, that's good for Google, not bad.

Now, that's not to say Chrome's popularity isn't an issue. We need more diversity and less centralization. But for a variety of reasons I find it hard for the same IE6 situation to repeat itself. The world in 2018 isn't the same at it was in 2002.

When Debian's Chromium is "no longer supported"

[DaveM753]

IMHO, it's particularly alarming when the Debian Stable version of Chromium is showing as "no longer supported" by Google Docs. I ran into this warning several times, and it's one of several reasons I had to break my addiction to Google Docs. I can understand Google's desire to add functionality to their Google Docs platform, but to break Docs' functionality in fairly recent versions of their own open-source browser baffles me. There are reasons I don't want to use Chrome, and prefer to use Chromium. When Google slaps limitations on my ability to use W3C standardized browsers and force me to use their non-standard browser, I get the feeling they're only going to do worse in the future - al la Microsoft.

And so, last year I decided to ditch Google Docs and go back to LibreOffice. The most painful aspect of this is the loss of world-wide, easy access to my documents. Leaving the cloud is a hassle, but it's better than vendor lock-in.

Not exactly Internet Explorer.

[DrYak]

There's a difference.

Internet Explorer back then, locked you into a shit ton of closed source proprietary secret poorly documented stuff (embed OLE objects/ActiveX extensions night mare).
There was no sane way to make a web app specifically made for IE to run on anything else except the specific version of IE that it was made for.

Google Chrome mostly relies on open standard. Take another browser that complies with the same open standard, and you can more or less access the same web apps.
Chrome's source code is even accessible. When in doubt you can check how they've implemented some non-compliant stuff.
In practice, very few web apps run in Chrome but completely fail in Firefox, despite both using entirely different engines.

Yes, a lot of web apps fail in Microsoft Edge /Internet Explorer or in Safari, but has more to do with those being bullshit browser which aren't up to date with standard (microsoft's stuff even more so) than Chrome being a proprietary target.

And then, there's the whole anti-trust / profit angle.

Back during the internet explorer scandals, Microsoft was profitting from selling software. By making sure that as many websites and webapps only work exclusively with IE, Microsoft made sure that people desperately need to buy Windows from them in order to get the bundled in Internet Explorer.

Nowadays, Google doesn't profit at all from Chrome. Their hugest profit driver is matching *results* (though not the search results themselves in Google.com, mind you. But matching ads to serve best to end users. And matching content to keep youtube users hooked while they play ads. etc.)
They don't give a shit if you use their browser. They want to use *a* browser, *any* browser, might as well be Firefox if not Chrome (which they *also* finance - Google is pouring money and financing what some could wrongly consider their "main competition").
As long as you end up using this browser to go online, where they can thrown ads at you and sell your eyeballs to the highest bidding advertiser, and where they can monetize the shit out of all the online behaviour data they can gather about you.

Chrome isn't a product on which Google is making money (directly).
Chrome is just one of the possible tools that make their actual business (profiting of users going online) possible.

You can hardly suing them for antitrust violations, Chrome is free (i.e.: "gratis" as in beer) as well as major part free software (i.e.: "libre" as in freedom to look into it and build your own browser).

Re:Not exactly Internet Explorer.

[lgw]

There's already too much Chrome-specific stuff and the point is: it's growing. Sure, Chrome started as fully standards-based, but then so did IE in the (very) early days when it was the best browser around. Then the years went on, and the IE-specific stuff grew until we had the world of IE6.

Chrome is starting to look like it's on that trajectory. Sure, it's still mostly standards-based, but its trajectory is away from that, and in fact looks very much like the trajectory from IE3 to IE6.

Finding web apps that aren't even trying

[CruisinAdam]

We recently had a product forced on us by our state government that they had written by and outside contractor. Everything works fine in Firefox with a user agent switcher, but otherwise you are blocked with the message "Google Chrome is the only supported browser..." I get the feeling it's people who can't be bothered to test their code in anything other than Chrome.