This post is kinda annoying to respond to. Not because of what you said, but because it’s hard to map my intuitions into words and convey exactly what’s wrong with Windows in the first place.
Linux doesn’t require immediate rebooting, it assumes the user will choose the right time. And if Microsoft actually gave a shit about user autonomy, there are smarter ways to handle updates.
For example: instead of forcing updates in the middle of the fucking day, just wait until the system would normally sleep or hibernate, or when the user is clearly inactive (like at night). At that point, the system could save the current RAM state to disk, reboot with updates applied, and restore the session exactly as it was.
This isn’t sci-fi. NixOS can already do this (barring kernel changes). The fact that it works proves the concept is viable.
before anyone fucking @'s me… I get that saving RAM state across system updates could break shit. But it doesn’t have to, especially if you implement a tagging or compatibility layer to track what’s safe to resume. That kind of bridging isn’t impossible, it just takes planning.
FOSS software routinely considers edge cases like this. Microsoft doesn’t. That’s not a tech limitation; that’s just not caring about user convenience.
For starters, instead of forcing updates in the middle of the fucking day, simply wait until the computer would usually sleep/hibernate, or the user wasn’t using the computer
I think that’s what active hours is supposed to do
This post is kinda annoying to respond to. Not because of what you said, but because it’s hard to map my intuitions into words and convey exactly what’s wrong with Windows in the first place.
Linux doesn’t require immediate rebooting, it assumes the user will choose the right time. And if Microsoft actually gave a shit about user autonomy, there are smarter ways to handle updates.
For example: instead of forcing updates in the middle of the fucking day, just wait until the system would normally sleep or hibernate, or when the user is clearly inactive (like at night). At that point, the system could save the current RAM state to disk, reboot with updates applied, and restore the session exactly as it was.
This isn’t sci-fi. NixOS can already do this (barring kernel changes). The fact that it works proves the concept is viable.
before anyone fucking @'s me… I get that saving RAM state across system updates could break shit. But it doesn’t have to, especially if you implement a tagging or compatibility layer to track what’s safe to resume. That kind of bridging isn’t impossible, it just takes planning.
FOSS software routinely considers edge cases like this. Microsoft doesn’t. That’s not a tech limitation; that’s just not caring about user convenience.
I think that’s what active hours is supposed to do
I think the operative word phrase is “supposed to”
Anecdotally… It doesn’t seem to exist.