this post was submitted on 17 Mar 2026
26 points (78.3% liked)
Linux
12911 readers
810 users here now
A community for everything relating to the GNU/Linux operating system (except the memes!)
Also, check out:
Original icon base courtesy of lewing@isc.tamu.edu and The GIMP
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I could see it becoming the future. But only under a couple of scenarios.
Scenario A: It becomes (strictly) better and/or easier than the alternative. Kinda like how systemd effectively replaced SysVinit within a couple of years, simply because it was a more sane alternative. But this is reliant on the read-only aspect being put in place without affecting existing workflows on traditional distros. So, as Fedora Atomic is the atomic distro I'm most familiar with, I'll provide explicit examples from it:
dnfshould (somehow) continue to function. It could even be an alias (or something) that invokes something else entirely. I don't even think most users will care for what exactly happens in the background, as long as the functional expectation is being met.Scenario B: It's enforced on us by (some of) our Linux overlords and/or expected by (parts of) the Desktop Linux stack. Kinda like how the GNOME desktop environment currently has dependencies that are systemd-components. Thus, requiring some hacking to make it work in its absence. Currently, I can only see some RHEL(-adjacent) projects committing to this.
But I think both of the above scenarios are at least 5 years away. While atomic/immutable distros enjoy a healthy (perhaps even generous) amount of development, AFAIK none of them are actually 100% feature-complete^[To be clear, it's probably at like 95% or so.] compared to their traditional counterparts. So, fixing (most of) the remaining edge cases to make migration possible for every enthusiast that even considers switching, should probably be their priority.
It's definitely getting there.
I found the regular Fedora SilverBlue install did not give enough flexibility to be very usable. The suggestion to just use toolkits is not for mortals. I copied Bazzite and installed homebrew (coming from Mac, that's comfortable). Brew solved 95% of the pain.
The next annoying 4% was stuff that doesn't work well with flatpack: Steam, gamescope, password managers, etc.
Then there's a final 1% of the masses of content written about Fedora using rpm and dnf that just kinda doesn't work. Makes stuff like following a build guide or install steps a little bit more annoying.
The really nice thing about it though is I was able to switch between different fedora environments and bazzite with relatively little pain. Nothing really broke, which was great.
If the future of the desktop is linux, it needs immutable distros to get really good. Personally, I wouldn't want to go back to fully-root-editable linux, but I also do not blame the folks (who want to) to be able to nuke systemd and Wayland (which both do too much for my taste) and do their own thing.
Overall, I wholeheartedly agree with your assessment.
I am also not convinced that it was ever meant as the endgame. Like,
toolboxstill doesn't offer a mechanic to upgrade a(ll) container(s) without entering one. The last time I used it, it also shat itself whenever the old pet container became EOL and desired a 'system update' to become functional. IIRC,distroboxdoesn't fare any better at this. Thus, coming with what looks like planned obsolescence; with the recreation of the pet containers every couple of months as a result. I suppose the solution is picking an image that's supposed to be rolling-release. Which is why I think this workflow suits Aeon better.