It goes like that until the update changes the kernel version and breaks a video driver. I mean, it’s a lot rarer than it used to be, but our arcade box at work just got hit with it.
Windows usual fail mode (which is often) is update won’t process so it wastes an hour of your time a bunch of times and either justs starts working or requires you to dig into it and either run it manually, or clear up some cache.
Windows not booting into a gui on an update is pretty rare.
Homie, if a kernel update breaks something you can just boot back into the older kernel from grub. It literally only takes the time to reboot the computer.
Yeaaahhhh, i’m a disagree with this one a little.
It goes like that until the update changes the kernel version and breaks a video driver. I mean, it’s a lot rarer than it used to be, but our arcade box at work just got hit with it.
Windows usual fail mode (which is often) is update won’t process so it wastes an hour of your time a bunch of times and either justs starts working or requires you to dig into it and either run it manually, or clear up some cache.
Windows not booting into a gui on an update is pretty rare.
Homie, if a kernel update breaks something you can just boot back into the older kernel from grub. It literally only takes the time to reboot the computer.
Until you roll back and shits broken now because the new kernel was a requirement on other shit that was in the update.
For my own shit, I’m running nixos, so when I roll back, every app that just got updated rolls back, perfect recovery, but that doesn’t work for most.
As far as the pop-os that broke the other day, I’m more than capable of depsolving and fixing it, but it’s not ideal.