• Arthur BesseOPMA
      link
      fedilink
      arrow-up
      7
      ·
      2 years ago

      i don’t see why the concept of building immutable images using existing distro packages and tools shouldn’t apply equally well to nixos and guix as it does to deb and rpm distros.

      • hfkldjbuq@beehaw.org
        link
        fedilink
        arrow-up
        2
        ·
        edit-2
        2 years ago

        Nix and Guix are already reproducible and have immutable store; no need for images in that case, and they more flexible. I’d need to read the article more throughfully for the deployment argument

      • Ferk
        link
        fedilink
        arrow-up
        2
        ·
        edit-2
        2 years ago

        My problem with this idea is that I generally do not like the defaults most distros use, I like experimenting and I often switch desktop environment or uninstall / clean up stuff I don’t need.

        I’d be ok if the image is just kernel + init system + shell, and maybe some small core components / tools… but if the OS comes preloaded with huge software libraries, like typical KDE / GNOME distros do, then it’s gonna be a lot of dead weight that I’d have to keep updated even if I do not use it.

        Immutable images are great for devices with specific purposes meant for a particular software stack (like Chrome Books, the Steam Deck or so) but for a more general purpose computer where I actually want to deeply customize the UI for my workflow, I don’t want to carry around whatever popular software the maintainers of the popular distro might have decided to include.