5 ms·
And this "inventing your own launcher/updater" fetish that seems to be pervading software. There is a corollary to Zawinski's law here: every piece of software
by zamalek 6y ago
And this "inventing your own launcher/updater" fetish that seems to be pervading software. There is a corollary to Zawinski's law here: every piece of software eventually installs yet another shitty updater alongside itself.
Fuck the perfectly functional updater built in the Mac store.
- coldpie 6y agoYeah, for all the complaining we do about the various app stores, shitty devs like Adobe really forced the platform vendors' hands on this. Users and devs can't be trusted with that capability, the platform vendor needs to be the adult in the room.
- vageli 6y ago> Yeah, for all the complaining we do about the various app stores, shitty devs like Adobe really forced the platform vendors' hands on this. Users and devs can't be trusted with that capability, the platform vendor needs to be the adult in the room. It doesn't even have to be like this though. Why not a simple notification directing me to the download? I guess reduced friction but is that really it?
- chii 6y agoif done well, an updater is fine. See chrome/firefox's updaters.
- zamalek 6y agoThose updaters do work great, probably because (at least on Windows) they circumvent elevation by not requiring it. The problem is that, if every app decides to use its own updater, there's a good chance that your internet line could get saturated when everything decides to update at once (especially when this awful PDF reader is 180MB). A system-wide updater avoids this issue.
- renewiltord 6y ago30% revenue cut so that you get no increased market? Yeah, fuck the perfectly functional updater. The dollar loss through distributing a security flaw is way lower than that.