These days i was wondering how good atomic is (using SB for like 2 years) but how bad is the need to reboot every dam time to get a update.
i usually just use flatpaks or stuffs installed in toolbox (base almost clean) but still got plenty of updates (would say almost everyday), with security tag (making the need to reboot a priority)
I cant see a mass adoption in a system that need to reboot every time hence the question .
i like the concept of atomic, not the part of the reboot, is there on the future roadmap of atomics any possible way that would make updates without the need of reboot ?
One consideration is the kernel update pace. When kernels are updated, sometimes as often as weekly, it is mandatory to reboot (with all spins) in order to use the new kernel.
The atomic systems must reboot with every update since the system is a single ‘atomic’ build. If you do not like that forced reboot with every update then I suggest using one of the non-atomic spins which do not require a reboot with every update, but only for certain items such as drivers, kernels, and certain other system critical packages.
another solution that i could think is some sort of saved session, like opening apps and windows in the exactly place they was before reboot. I guess it would depend on DE, but if fedora could ship some tool that could do that (if exists) would help a lot
i used to use regular fedora, but found after changing DEs and installing and uninstaling certain packages, system got messy/clunky making the need of reinstalling regularly in some sort of time (usually when new version release) found in atomics a way out to this making the base clean