What are immutable distros, and are they the future of Linux?
What are immutable distros, and are they the future of Linux?
Head to https://squarespace.com/thelinuxexperiment to save 10% off your first purchase of a website or domain using code thelinuxexperiment Grab a brand new laptop or desktop running Linux: https://www.tuxedocomputers.com/en# 👏 SUPPORT THE CHANNEL: Get access to a weekly podcast, vote on the next t...
love this guys videos, just watched this one earlier today
Colossal waste of developer time and system resources. No thanks. At that rate just port the whole userland to nodejs electron too.
Personally I'm not super into the idea of immutable Distros, they kind of feel like Phone or Game console operating systems due to being read-only and containerized.
I prefer being able to change stuff without it being overwritten in the next update which is one of my many complaints with the steam deck and it's immutable OS, the system is locked to read-only and even if you unlock it it'll get relocked and all your changes undone at the next update.
It is actually pretty fine for steam deck. It's has to be a console like experience.
For a desktop os? not so much
Well on my SteamDeck I wanted to install Portmaster for Adblocking and network filtering, and also wine because running Windows apps with a click on the Desktop > Opening Bottles and setting each one up before, Also wanted to switch KDE for Gnome because KDE sucks on a touch screen big time where Gnome is much more touch friendly. Also wanted to install neofetch as well but just ran it as a script to get what I needed. Yes I can disable the read-only and do it all anyway, it's not really locked down but because SteamOS doesn't respect or honor changes they'll just undo it whenever I update.
The point is you don't need to change stuff. You tell the resulting state of the system, the system will generate that state for you.
You don't change some file somewhere, you change the pipewire settings in your configuration file and rebuild. You save your config to version control so you can recreate the exact copy of your system any time and on any computer by just letting it download the locked versions of all of the packages you have installed.
Well back when I didn't know any better and would go through linux installations because I would break things but also because many of the "recommended linux distros" had problems (f*** you Canonical forcing buggy snaps onto us) I might've thought it was an awesome idea. But now that I know better (both how to not break stuff + fix things if they're broken, and know when people are recommending glitchy trash) it just feels more restrictive. Kind of like a game console, android phone, or S mode. It's not necessarily as restrictive as those things because you can turn it off and do what you want but the updates to the OS will almost never respect the changes you make, as I know from SteamOS.
Because I want to Install portmaster or create services to launch my own scripts on Boot without them being purged blindly by an update (just like How on Game consoles System updates will remove installed homebrew) I'm not into the idea of using immutable systems that lock you out of changes you might want to do that aren't official.
At least in coreos. rpm-ostree let's you "layer" packages on top of the base image, so when you install the next update it will automatically install your packages on top. You get to have the cake and eat it too.
Nick is probably my favorite Linux YouTuber. He seems to be the only one to understand that Linux has to look and feel sexy for new people to stay on board.
How’s this different from Docker over LXC in terms of practicality?
Docker and guis are not great friends. Docker containers are mainly for web services
If a lot of people don't prefer immutable distributions, why are they made? I still don't understand who this is for.