Just some rando notes from my first almost deep dive into immutability. All very exciting and the various projects seems to be solving the same problems with clever tools that really makes you wonder why the big old kitchen sink OS install is still around.
As often mentioned in the various docs and talks: why aren’t our desktops as lean as our phones and tablets or thin clients (of the past?), why are so much effort ‘wasted’ if you will on myriads of package and config adjustments to solve more or less the same trivial user needs?
Perhaps my perception of the value proposition is exaggerated and the workhours req. to nurse non-immutable OS’s aren’t that crucial in the total time and resource budget for most users and businesses. But think about all the hours spent/wasted on tinkering and horrible update cycles and OEM blunders, change management must be a nightmare at MS for instance.
Run Distrobox on Fedora Linux - Fedora Magazine led me to Portal:MicroOS - openSUSE Wiki which, at 2.3GB isn’t that micro but somehow that ended up on the disk before Silverblue. AFAIU it’s similar to Silverblue minus ostree, with btrfs instead to snapshot disaster rollbacks.
Btrfs conquered the disk immediately and I couldn’t get the usual
df -h overview but anyway, the Flatpak software store was up and easy to pick up some daily driver apps from. Again, not knowing Flatpacking, hard to tell how much disk space and how many processes was initiated. Are they there after a rollback? TBC.
Their podman driven toolbox seems similar to what I’ve read about Silverblue/FCOS. Userspace also noob confusing, installing emacs in a toolbox creates configs in /home/user/.emacs, not sure where else they should be tbh, was maybe expecting something like overlayfs or chroot methods to take the traces with them when leaving the toolbox. Flatpak emacs was confused as well. I guess a proper podman env. can solve that somehow if needed.
FCOS remains a better solution (starting from almost scratch, scalable to infinity) in my beginner mindset when (config) managed in a way similar to the guix/nix pioneers who seems to be able to roll out and keep track of anything with clever declarations. Looking fw to learning how to do that the FCOS way, high hopes. Maybe that distrobox thing can keep track of the DE in a smart way and keep it separate from the precious core.
Value proposition II, on the phones and tablets analogy:
Consider all the devices out there already and what ‘most people’ really need as daily driver tools. Except for gamers and VR/AR robotics stuff noone needs more CPU or RAM to do what they need to do, from now on and forever.
Consider Android without Google’s business model, when that market is finally (!?) depleted, who can streamline a Android-just-nice OS codebase that can be rolled out on any device you can get your hands on and networked to better usage.
Consider some kind of future energy crisis hitting datacenter costs all the way to the user’s budget. We’re gonna need some kind of standardized deployment that makes desktops as scalable as containers are today.
yadayada ladida almost-reddit-rant-coffee-thoughts /out
Thanks again to all the FLOSS devs who made all of this fantastic tech possible and available.