How many times has a new update "broken" things on your machine? I prefer to install the updates when I choose to, not when Google chooses to.
Now to address some of the inaccuracies I see in the previous postings...
Those of you comparing the Google mechanism to Apple's update mechanisms are way off base. (Windows AND Mac versions)
Unlike Google, Apple clearly tells you up front that it wants to install a software update mechanism and gives you the option NOT to use it. Windows users who claim it automaticgally turns itself back on when you turn it off need to loosen their neckties and get some oxygen up to their brains. This just isn't accurate.
And enough with the phony claims that Apple sneaks software onto the user's machine. That's just not true either. They are VERY clear about what is being installed and always offer you the option to NOT install the extra software.
On the Mac, Software Update can be configured NOT to automatically install updates, and there is much transparency regarding the update process. It isn't sneakily hidden in the background. They are up front about it.
On Windows, you can easily configure the software update mechanism to ignore updates and never darken your door again. Use the prefs, folks. That's what they are there for.
Next, what on earth (the real one, not the google one) does google need to be doing in the system space. This is an end user app. There is no reason that the update mechanism can't reside within the app. Why do they feel the need to install a system level daemon to accomplish the task. (Yes, I know they are not alone in this respect. I resent it just as much in the other vendors as well.)
So let's have an accurate discussion about this. I DO think Google has crossed the line here and I don't think the comparison's to Apple's approach are valid.
"Well I don't see why I have to make one man miserable when I can make so many men happy." -- Ellyn Mustard, about marriage