Atomic Linux Distros: What Barriers Stand Between You and Making the Switch?
lambalicious @ lambalicious @lemmy.sdf.org Posts 9Comments 834Joined 2 yr. ago
lambalicious @ lambalicious @lemmy.sdf.org
Posts
9
Comments
834
Joined
2 yr. ago
For me it'd be two aspects:
For (1), it's not necessarily about the explicit workflow, like the GUI apps and stuff; but also the implicit workflow as well: the stuff going on with the machine because you are not touching it (even if it is because you've touched it before).
Some examples. I need to forbid PA and have either ALSA or Pipewire (or both) with alsa-ucf disabled because of a hardware bug in my machine's audio chipset. I can one-time accommodate the required kernel boot time options and ALSA configs without issue on Debian, can I do that on an immutable? Am I forced to the barely-progressing-past-failure that is wayland, or can I use the Xorg setup that has for decades proven to me to work? Do I get to escape the enforced GTK compose key mapping on my own, or do I need to break immutableness to fix it? Can the programs that I launch through wine on the user account I set up for work, interact with the apps I have on my normal user's desktop (incl. copy-paste, desktop screenshots, sending global key events for stuff like Teamviewer, Supremo, Anydesk), or do I need to fall back to a Virtualbox VM?
And for (2), it's quite simple. I have a 8 GB RAM machine. I'm barely managing to survive this world of nu-web development where hello world apps download 150 MB of a typokit SDK from Cloudflare or something. If an immutable environment means that everything even the Linux equivalent of W95's notepad.exe is now containerized, that's an extra memory and resource overhead that my system likely can not serve and that I don't really have an use for anyway (why would I want a text editor to not load up a text file I told it to load???).