| Because I hate it when features are irreversibly changed, at random. Which is what happens with "evergreen" software. I don't care if it only happens occasionally. Never is better than occasionally. I want the peace of mind to know that if something stops working, that it's not because of an update. If you're going to introduce feature regressions, you'd better at least make it easy to undo them. If you're going to make users update on your schedule, you'd better be really really good at making your updates smooth. Google can almost get away with this, but Dropbox, OneNote, Skype, and especially Firefox have introduced major bugs without telling me. Firefox is the worst offender, because even if you explicitly disable automatic updates, it will just repeatedly download updater.app anyway.
I discovered this when I had to fix something on a 3G cellular connection on a strict deadline. Another morning, I woke up to find a bell icon added[1] next to my clock, with no obvious way to remove it. It brought me back to the bad old days of Windows 98 where drive by installers would just add stuff to your computer. Eventually, I just chflags -R schg /Applications/, and ripped out all of the updater daemons out of frustration, and I'm happier ever since. The thing I object to the most, is for software you already have installed to have features removed and replaced with a nag to buy back the features you just had before the update. LogMeIn's Hamachi app did that, but thankfully I keep backups. Or, a classic example from a long time ago, was iTunes 4.01, which had an "emergency" update for iTunes 4 that removed the local network music sharing feature. [2] Think about what's really going on with the updating ecosystem we have. Are you really OK with software like the deceptively named "keystone agent" running as root, that can add and execute data anywhere on your filesystem? Google Drive and Google Earth will try to reinstall it if you remove it, and nag you with deceptive messages about how they need you to authorize superuser access for them so that they can run properly, when in reality they are just adding the updater daemon, which they do not require to function. After having been burnt by new bugs, and outright dishonesty, I'm very careful now. [1] http://osxdaily.com/2014/03/30/disable-chrome-notification-b... [2] https://apple.slashdot.org/story/03/05/27/2114240/apple-upda... |