Comment #20 on issue 1565 by t...@crowdersoftware.com: Don't make GoogleUpdate always-resident http://code.google.com/p/chromium/issues/detail?id=1565
On the update curfluffle: I'm glad to hear the team are looking at fixing this problem. The keys to keep in mind for that are 1) Transparency, 2) Control, and 3) Resources. Transparency: The user must be told what the software is doing. This includes what it's installing, any schedule on which things will run, and notification when they're running (just a subtle "Chrome: Checking for updates; click here for options..." is fine). Control: The user must be able to tell the software what to do (including what NOT to do), and when to do it. Hence the "options" link on the above. Resources: As many previous posters have pointed out, all modern OSs have scheduling features. I don't care how little memory or CPU time GoogleUpdate.exe uses. There is simply no excuse for having it resident at all times. Personal preference: I really don't want even more things running at startup -- startup of the system, or startup of the browser. Usually when I turn on my computer or open a browser, I have something I want to do, and all of this junk running at startup is in my way. Use a scheduler, let me decide when (and if) there's a check for updates. -- T.J. Crowder -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs -~----------~----~----~----~------~----~------~--~---
