Add to that that you can work while the update is being downloaded and applied; and in the very few occasions where reboot is absolutely inevitable (I have never had such a situation since many years; even the new kernel can wait until I'm done with my things and ready to reboot to bring it online), it's just a reboot, nothing more. With Windows 10, it just blocks you with a screen that has a message telling "I'm doing my things now" and a progress report. Your work is inevitably interrupted.
For example, I sometimes play some games on my brother's Win 10 PC (I don't use Windows on my laptop, and don't want to bother with setting up Wine and the games on it). A couple days ago it wanted to update, and I told it to postpone. Then I left for 15 minutes and came back, there was an update going on. It blocked us out of the computer for the entire afternoon and most of the evening doing black magic behind a soft blue screen.
Re:Lobotomizing Gnome
by jamesgeck0 on Wednesday May 30, 2018 @02:27PM
(#17190210)
While I don't love Window Update's behavior, that particular major update was released about a month ago. Your brother has been postponing it for weeks.
While package management is a solved problem (well, on all platforms outside of Windows that is), that doesn't mean that occasional issues will not arise. Though for what it's worth: I run Arch which is about as hands on as it gets without compiling your own packages and it's been 10 years since the last time a package update cost me 45 minutes or longer of my time.