3 ms·
I've never been entirely sold on how awesome Chrome's invisible updates are and this is exactly why. It's great as long as they don't push any bugs through. B
by prewett 15y ago
I've never been entirely sold on how awesome Chrome's invisible updates are and this is exactly why. It's great as long as they don't push any bugs through. But once they do (and it will happen), there's no way of using a known good version. So if I'm IT in charge of 10,000 users at MegaCorp, I cannot make any promises about reliability of internal web apps with Chrome, because at any point Google could break something.
(Obviously you can work around this by providing snapshots of Chromium, or Chrome binaries patched to not update or whatever)
- deleted 15y ago[deleted]
- sixcorners 15y agoFirst google result: http://www.sitepoint.com/how-to-disable-google-chrome-updates/ http://www.sitepoint.com/how-to-disable-google-chrome-update... Does this not work anymore? Are you privy to something I don't know?
- prewett 15y agoI didn't know about this, but I don't think it solves the issue. Disabling updates allows you to stay at the current version (or, by enabling updates, go to the most recent version). But you can't get any particular version. Suppose I know that version 12.1.3.135 works perfectly for my internal application but that the current doesn't for some reason. How do I get that version? With versioned software this isn't so much of an issue, but with Chrome's continuous versions, it's a little harder. And how would one roll that out to 10,000 users? I'm sure it's not terribly difficult, but not as obvious as giving everyone Firefox 8. And what happens when the CEO decides to enable updates and it breaks your web app?