I’ve read that containers are preferred for development, but they aren’t persistent and it doesn’t seem like files such as /etc/fstab can be accessed through them when running distrobox (I enjoy editing such files using vim).
It’s also a bit annoying having to enter a specific container to run something like btop.
Are you supposed to layer them with rpm-ostree?
I’m not sure.
I’m a professional tinkerer and I run Debian stable. OK ok it’s not an immutable distro but my point is that I do tinker, just NOT with my main OS.
I’ll tinker in containers, in VMs, in my ~/bin etc but NOT in what hosts all that.
So I would argue that what’s important for tinkerers is to establish clear boundaries on what they want to tinker on and what they do NOT want to tinker on, what can change vs what should never.
But a simple thing like “install a random cli tool to run on host” is often not easy on immutable distros, so it’s usually just more convinient with an oldschool distro in those cases.
I don’t think it actually is. It’s only like that the very first time when you haven’t you this specific distribution itself. Once you know how the few extra step and understand the core principle, it’s trivial.
PS: I did tinker with NixOS, SteamOS and ROCKNIX.
Sure. But you have to figure that out first.
I’m just saying. It’s not for everyone. I feel too limited when trying immutable stuff, so I stick with my classic. 😀
Is this rooted in experience? Or mostly just on vibes?