Not equally bad at all. Holding back Chrome versions means you need to keep track of Chrome vulnerabilities to stay safe. Holding back Chrome updates and cert r

Not equally bad at all. Holding back Chrome versions means you need to keep track of Chrome vulnerabilities to stay safe. Holding back Chrome updates and cert revocation updates means your security surface area includes every SSL website you use. There are plenty of good reasons to "bork its update process", for example if you work in enterprise and have a change management process for browser updates. Or if Chrome introduced a feature you don't like (like Lion fullscreen). Or if you prefer to use your OS's package management system for browser updates. It's not so much a matter of Chrome's update process as your update process. If that's "I want the newest version as soon as it comes out, all the time", then great, but there's no guarantee that's true. That's the exact reason Firefox is doing its whole ESR thing.