You say that, but Discord will happily refuse to open until you download the latest .deb file from their website, and it’s one of the friendlier Electron applications in terms of in-window updating in my experience.
I had to disable my adblock to get the Teams application to show me a button I needed at some point…
One interesting thing I’ve heard from people I’ve introduced into Linux is that you need to reboot an awful lot. It has to do with automatic security updates triggering a reboot-required flag, but every other day I get a popup with “updates were installed, you should reboot”.
Linux distros usually raises a reboot required flag. But thats usually to complete some kernel or system update. Windows just go ahead and reboot on update ruining the workflow.
When you get the message to reboot ignore it and do your work. Then shutdown after doing it. Turn on when you need it the next time. And its all well
Ignoring the reboot doesn’t work when it’s a reboot to the Nvidia driver, as I’ve found out. The displays will work but Vulkan/OpenGL will break in confusing ways with error messages that point in the wrong direction.
I don’t really understand why more Linux don’t hot replace the kernel, Ubuntu can do it and so can a bunch of enterprise Linux variants. I assume there’s some kind of design limitation that prevents other distros from using that API.
You say that, but Discord will happily refuse to open until you download the latest .deb file from their website, and it’s one of the friendlier Electron applications in terms of in-window updating in my experience.
I had to disable my adblock to get the Teams application to show me a button I needed at some point…
One interesting thing I’ve heard from people I’ve introduced into Linux is that you need to reboot an awful lot. It has to do with automatic security updates triggering a reboot-required flag, but every other day I get a popup with “updates were installed, you should reboot”.
There’s a configuration file you can edit to prevent that. The Flatpak configures this automatically for you.
Linux distros usually raises a reboot required flag. But thats usually to complete some kernel or system update. Windows just go ahead and reboot on update ruining the workflow.
When you get the message to reboot ignore it and do your work. Then shutdown after doing it. Turn on when you need it the next time. And its all well
Ignoring the reboot doesn’t work when it’s a reboot to the Nvidia driver, as I’ve found out. The displays will work but Vulkan/OpenGL will break in confusing ways with error messages that point in the wrong direction.
I don’t really understand why more Linux don’t hot replace the kernel, Ubuntu can do it and so can a bunch of enterprise Linux variants. I assume there’s some kind of design limitation that prevents other distros from using that API.
But I think you can ignore it, the updates just will not take effect until you reboot.