|
|
|
|
|
|
by davvolun
2401 days ago
|
|
|
Exactly, and when the workaround is "just use one of the other 3 or 4 major browsers that are probably already installed on your work computer" (and if you're using an enterprise setup as mentioned in the article, you've probably got 2 or 3 things that are still locked into IE, probably IE6 for some stupid reason). If your business is so locked into using Chrome, and specifically Chrome, and you aren't paying money to Google to ensure it keeps working as you need it, then you have only yourself to blame. (And yes, being unable to disable the experiments thing, and not giving any warning before-hand, is a mistake on Google and the Chrome teams part, and hurts Chrome's enterprise-ready image, but that doesn't refute the point above). If an essential piece of your business relies on something you have no control over, then you only have yourself to blame when that reliability fails and you can't fix it. Cost of doing business, at worst. |
|
|
The problem with Chrome is that developers push each other to use Chrome, so they only develop for Chrome, and the stuff they make might only work in Chrome.