That would mean doing as much of the work as possible in the background in a way that doesn't impact the user and making sure the reboot where it actually gets activated doesn't take noticeably longer. It would also mean not doing things that are against the user's interest like moving things around, installing new ads or misfeatures, or breaking things.
I don't know anyone who hates or wants to disable Chrome updates, for example (I'm sure such people exist, but it's much less common than Windows updates), despite Chrome updating way more often than once a month.
Of course, overcoming the aversion people built over years because of past bad behavior is going to be hard, but forcing people against their will and making updates more disruptive isn't going to help with that aversion. People really dislike being forced to do something, even if they don't actually mind the thing itself that much.
Android does an A/B update and after a only slightly slow reboot is in the new version. It then does some optimization in the background that can have a slight performance impact.
NixOS must be the gold standard here. It downloads and completely installs the new version in the background then a regular-speed reboot is enough to be running the new system. (~10s on my system)
But Windows and macOS both have crazy slow update processes. When I had a mac for work I was dumbfounded by how slow the update process was. It regularly took >30min! Those machines are crazy fast, it seems like it could have written a TiB of data in that time so IDK what it is actually doing.
Point updates of macOS take 20+ minutes on an M1 Max with 32GB of memory and a blazing fast SSD. What could it possibly be doing?
Even iOS updates are a bit faster.
Is apple even interested in fixing this?
If memory serves: point-symbol optimizations to make code calls into The objective-C libraries performant.
Under The hood, objective-C really does use strings to reference library functions. So when the OS is updated, the string interning table is updated and all of the installed software has to have its string to symbol caches rewritten to account for the new API.
There are almost certainly better ways to do this but if I understand correctly, Apple inherited the existing solution without putting enough thought into how it would scale and now changing the solution would break an indeterminate amount of software depending upon the current implementation.
EDIT: a sibling comment jogged my memory; the thing I was doing a bad job of remembering was prebinding. https://opensource.apple.com/source/cctools/cctools-622.5.1/...
When a new version of the OS is installed, the OS re-runs prebinding for applications to the dynamic libraries they rely on because the dynamic libraries may have changed. The alternative is to have a big latency bump every time an app is launched for the first time as the caches are rebuilt on-the-fly.
(I think this is the step that used to be called "Making Your Macintosh Happy" during an install, but the veracity of that notion has fallen too far down the Google search hole for me to easily pull up a reference to confirm or deny it).
However, this exposes the real challenge. We cannot have informed consent without informed users. I think this problem will haunt us repeatedly in the future. We need users to know at least a little bit about their options. Only then can they make informed choices on what option to pick. This means people can't glaze over the details and not worry about them. This does not mean you have to be a computer wizard. You just need to know what you want and pick an option that is good for you. For example, I run this on Fedora:
sudo dnf offline-upgrade download -y && time sudo dnf offline-upgrade reboot
I used to wonder why no corporation complains about Windows Update. Then I learned that virtually all companies use group policy to change Windows Update behavior to suit their organization. Therefore, this is a non-issue for them. Welp.
That also includes never crashing, which Microsoft has historically struggled with.
If you don’t reboot in an orderly way, then the machine crashes while the user is doing something, and when it restarts everything is different. “Don’t restart” is insufficient for good UX here.
You can still choose to reboot for every update. The point though is that it is a choice.
sudo dnf offline-upgrade download -y && time sudo dnf offline-upgrade reboot
Here is what I understand about dnf offline-upgrade
> The process of restarting, applying updates, and then restarting again is called Offline Updates. Your computer boots into a special save-mode, where all other systems are disabled and where network access is unavailable. It then applies the updates and restarts.
https://fedoramagazine.org/offline-updates-and-fedora-35/
> With Windows, it's an almost-weekly, "Hey, update right now, because someone in another country is pwning all unpatched machines that aren't air-gapped from the internet."
I see. I feel like I don't quite understand the extent of the problem. In any case, I am not qualified to even attempt to propose a fix. My mode of thinking was Google Chrome and derivatives are able to slowly walk along with increasingly scarier visible warnings asking users to restart the web browsers but they don't (as far as I know) reboot the web browser while the user is still using it. Even Google Chrome OS didn't do that (well, it didn't back when I had my cr-48). When I updated Mozilla Firefox on my Fedora machine, existing tabs continued to work. New tabs would come with a warning for me to close Firefox and open it again. This is the kind of warning I was getting rid of with offline-upgrade.
I agree with my parent comment though. Updates are too bloated. Windows updates should be very fast with a modern processor (Intel eighth gen, AMD equivalent or greater), enough memory, and a fast SSD. Even DNF which has a very renowned reputation (at least among Fedora users) of being slow, is pretty reliably fast. I think the point that my parent comment was making was make people not dread rebooting their machine. My thought was
1. educate the users why reboots are essential 2. allow the users to postpone reboots indefinitely
However, I don't know what to say if there is an active remote command exploitation in the wild. It is important to get the update to the user before the exploit. However, that goes against everything I've said so far. I guess this leads us to the status quo. Those who have the know-how to use group policy can opt out of certain Windows Update behavior. The rest can either learn to do this: and set up their own Windows Update server? Periodically check CVE and gate update releases? Not sure how it works...
The reason I hesitate and say automatic reboot should be OPT-IN is sometimes I like to do some simple long running task like stitch photos I took into a video using ffmpeg. It can take hours on a slow laptop processor. It would really suck to do something like that and come back to see the computer rebooted itself.
Chrome updates approximately every month unless there is a security issue that has to be pushed out faster.
That's basically not possible in some cases. Not all of us are on super-fast broadband, even in places that are nominally 'first world'. The _best_ my parents can get is 8Mbps on DSL. Every time an update starts auto-downloading, you know immediately because all other connections grind to a halt.
(Now why a minor point update security fix for Monterey is 1.6GB I have no idea. But presumably that's not something Apple is capable of/interested in fixing)
That would be me for one. I hate it when google sneaks in privacy reducing preferences that are automatically turned on. I like to occasionaly go through settings to see what has changed and was surprised when an update showed up a whole host of new active features.
Why on earth should usb ports on my laptop be automatically exposed to any web page that demands it? Chrome can do that now. And not just usb/serial/midi ports, and motion sensors, chrome has also enabled 'presence' (a way for sites to know when you're actively using the browser). I found that creepy.
More software companies need to get on board with the idea of having a separate maintenance branch and "next version" branch. Too many of them just develop on trunk and every time you update for bug fixes and security, you get all the other crap their developers have been working on too.
Too many instances of installed Linux distros breaking because some foo relied on some bar that the distro declared should work fine but must have slipped through the testing cracks somehow. Or I'd gone off-book on some custom project or other because it relied on library versions that weren't in the distro, then I forgot I did that and updating the distro libs broke my project.
I basically never run the apt updates these days.
Just to be clear, this isn't an argument that as a result updates should be forced.
The only real way to address it without the mandatory updates was for the ecosystem to diversify; can't use a Windows exploit to compromise a Mac OS machine.
You can imagine why that solution was not on Microsoft's list of recommendations.