In fact, if you can't afford the restart even when you schedule it, there's ksplice and a variety of similar solutions that can switch to a new kernel without a restart.
I did have firefox behave weirdly once after an upgrade until I restarted it, around v15 or so -- but I believe even that is no longer an issue; at the very least, I haven't had any issue with upgrading firefox while using it, and restarting it a week later.
But whatever windows does is way worse, I dread seeing the "please wait while Windows is configuring your updates" screen. I have an SSD, rebooting Windows takes less than 30 seconds, it's a non issue. But those update installs can take a long time and your computer is completely unusable while that happens.
It's also frustrating when that happens while shutting down because I normally turn off my computer's power outlet when I'm done (it switches off the rest of my equipment) so I have to wait patiently for Windows to allow my computer to shutdown before I can do that.
Well, how do Linux and other unices do that?
If you never restart a Linux desktop (or at least log out), you will be running outdated libraries, even if you run updates in the background.
(The best solution would be what Android does, where every program is supposed to know how to checkpoint itself, and they are forcefully restarted on a upgrade, transparently to the user. But even there, updates to system libraries still require a full reboot.)
services: they are specifically designed to be updated and restarted
I write plenty of daemons (you call them "services"). What exactly do I write specifically for them to be able to continue to run when a library is upgraded?
I don't think systemd supports what you are asking but it shouldn't be too hard to write a service that restarts other services if their shared libraries change?
From what I know, Windows doesn't allow a library to be replaced until it's not used by anything, which is more intrusive and is IMO the root cause (though indirect) why people hate updating Windows.
Their current solution is scheduling updates to periods when the computer is not in use. I think recently they added an option for you to define a set of hours where updates take place.
But the problem with this is that people don't treat Windows PCs like always-on devices like they treat mobile phones and tablets. So in those night hours the computer is off forcing daytime updates.