For instance, having to deal with desktop Windows’ BS. Oh, you wanted to play games? Well we have to take over your Steam Deck and install updates for the next 20 minutes.
I mean…sure you should be able to wait on the updates, but that’s not that common once you actually do the updates. And it’s not as if you don’t do updates on Steam deck (You absolutely should, and the flathub apps have tons of updates at least weekly when I run them)
That’s not the case, and you didn’t read what you linked. I’m also a professional system admin with decades of experience on Windows and Linux, so we can keep arguing if you’d like, but I’m not going to accept that Windows is as you’re saying when I know better.
What that link says is that I can delay the updates by a week on Windows 10, but then am forced to update after that. I can also set active hours, but the system will still force the updates and reboot the computer.
Linux can update without forcing a reboot until I’m ready. It also never has a “Updates Applying” screen that locks me from using it. And, in fact, most updates don’t require a reboot and the kernel can be setup for live updates that almost never require one to begin with.
Oh you’re not going to do the thing you then proceeded to do? Okay. How long did it take you to attempt a recovery from not being able to read the info in your last link?
For instance, having to deal with desktop Windows’ BS. Oh, you wanted to play games? Well we have to take over your Steam Deck and install updates for the next 20 minutes.
I mean…sure you should be able to wait on the updates, but that’s not that common once you actually do the updates. And it’s not as if you don’t do updates on Steam deck (You absolutely should, and the flathub apps have tons of updates at least weekly when I run them)
The important difference is that’s on my schedule when I want it to happen.
Steam does the update thing too, nobody is immune from that.
Steam’s updates don’t prevent me from using my PC, force me to run updates on their schedule or even require me to reboot when I’m not ready.
Windows updates don’t do that either, you have a choice when to install them, delay them, or just not do them.
https://support.microsoft.com/en-us/windows/manage-updates-in-windows-643e9ea7-3cf6-7da6-a25c-95d4f7f099fe
That’s not the case, and you didn’t read what you linked. I’m also a professional system admin with decades of experience on Windows and Linux, so we can keep arguing if you’d like, but I’m not going to accept that Windows is as you’re saying when I know better.
What that link says is that I can delay the updates by a week on Windows 10, but then am forced to update after that. I can also set active hours, but the system will still force the updates and reboot the computer.
Linux can update without forcing a reboot until I’m ready. It also never has a “Updates Applying” screen that locks me from using it. And, in fact, most updates don’t require a reboot and the kernel can be setup for live updates that almost never require one to begin with.
I’m not going to get in a certification dick measuring contest. Yes, you can in fact delay installation, and yes, you can schedule installation.
But really, an actual sysadmin knows you run a management tool for Windows updates:
https://learn.microsoft.com/en-us/windows/deployment/update/waas-manage-updates-wufb
Oh you’re not going to do the thing you then proceeded to do? Okay. How long did it take you to attempt a recovery from not being able to read the info in your last link?
Maybe just fuck off.