5 ms·
> What if an update silently breaks the update process? Hrm! This is part of why Chrome uses a separate application (Google Updater) to do the updating. Even i
by aboodman 15y ago
> What if an update silently breaks the update process? Hrm!
This is part of why Chrome uses a separate application (Google Updater) to do the updating. Even in the worst-case scenario where we update to a version of Chrome that can't even start, the updater still runs and can later update to a fixed version.
- riffraff 15y agowho updates the updater?
- bjc 15y agothe updater is self updating
- riffraff 15y agobut then doesn't this mean that parent^4's point is still valid? i.e. > What if an update silently breaks the update process? Hrm! If the updater is self updating an update may break it so that no further updates are possible.
- aboodman 15y agoSorry for slow response. I sure wish HN would mail me when people comment. Sure, the updater can break itself. But in practice, you rarely update the updater because the majority of the features you might want to update are in the app, not the updater. So you update the updater very rarely and cautiously, and you update the app quickly and fearlessly. It's not 100% foolproof, but it's a lot better than the alternative: Any crash bug anywhere in the application having the capacity to disable updates.