3 ms·
On the Mac side, Google uses http://code.google.com/p/update-engine/ http://code.google.com/p/update-engine/ I don't particularly care for this solution becaus
by js2 16y ago
On the Mac side, Google uses http://code.google.com/p/update-engine/ http://code.google.com/p/update-engine/
I don't particularly care for this solution because an update engine is started when the user logs in, and thus is running even if no Google application is. If you know what you're doing you can disable this and Google apps will still be able to update themselves when they are running.
Fortunately, I've not seen Update Engine used outside of Google apps. Most Mac apps use http://sparkle.andymatuschak.org/ http://sparkle.andymatuschak.org/ which I think is a far less intrusive solution.
- spatulon 16y agoIt's not necessarily intrusive just because it's running. I bet it's just swapped to disk and using ~0% of the CPU most of the time.
- js2 16y agoThere is no configuration for the update engine. It periodically checks for updates, and in the background will download and install those updates. There may situations where I don't want it doing so: e.g., if I'm on a low-bandwidth link. I can maybe understand this if I've got a Google application running, but to do so w/o any Google applications running is unacceptable. To be clear, I think auto-updating software is a fine default. But every other Mac app I have (since they almost all use Sparkle) will only update itself when running, and further, give me a preference to disable the auto-updates as well as specify how often I want update checks to occur. It is un-Mac-like to silently update in the background and w/o providing the user any control.