Distro agnostic packages like flatpaks and appimages have become extremely popular over the past few years, yet they seem to get a lot of dirt thrown on them because they are super bloated (since they bring all their dependencies with them).

NixPkgs are also distro agnostic, but they are about as light as regular system packages (.deb/.rpm/.PKG) all the while having an impressive 80 000 packages in their repos.

I don’t get why more people aren’t using them, sure they do need some tweaking but so do flatpaks, my main theory is that there are no graphical installer for them and the CLI installer is lacking (no progress bar, no ETA, strange syntax) I’m also scared that there is a downside to them I dont know about.

  • mosiacmango@lemm.ee
    link
    fedilink
    arrow-up
    2
    ·
    edit-2
    9 months ago

    I appreciate the breakdown, but you’ve basically made my point for me.

    The above, with its many advantages, versus:

    Sudo apt install X Y Z G F P -y

    Simple, clean, gets it done for near anyone.

    • Shareni@programming.dev
      link
      fedilink
      arrow-up
      2
      ·
      9 months ago

      Sudo apt install X Y Z G F P -y

      Debian 12 came out last June. In December the version of docker that’s shipped by Debian stopped being supported, and is now like 4 major releases behind nix. Debian won’t update it for at least a year and a half unless there’s some major security patch.

      Besides that, when Debian 13 gets released and I reinstall, I can just clone my dotfiles and use a single line to reinstall all of the packages I need. All of the packages are in a single list, and so there’s no more need to run health checks because I forgot to reinstall some random editor dependency for a language I use once a year. If I added it to the list it’s going to be on every machine running that list.

      • mosiacmango@lemm.ee
        link
        fedilink
        arrow-up
        1
        ·
        9 months ago

        Like most complex things in life, if you devout time to it and engage with it deeply you gain an advantage over a simplier version of the same thing. The question we all have to ask ourselves is “is this worth it?”

        I’d say in your specific “docker centric while using debain” use case, sure. Most people who use linux as a daily driver? Maybe not.

        • Shareni@programming.dev
          link
          fedilink
          arrow-up
          1
          ·
          edit-2
          9 months ago

          Like most complex things in life, if you devout time to it and engage with it deeply you gain an advantage over a simplier version of the same thing.

          What are you talking about?

          It’s just a list of packages, and an optional flake to control the repositories (stable/unstable) and add packages from outside of the official ones.

          To update everything nix related I just run:

          cd ~/dotfiles/nix/ && nix flake update && home-manager switch

          Sure, it’s slightly more complex than clicking a button in Discover, but it’s not rocket science.

          I’d say in your specific “docker centric while using debain” use case, sure. Most people who use linux as a daily driver? Maybe not.

          I’d say you’ve never seriously used a stable distro if you don’t realize how common issues like that are.

          I’m pretty certain the current hype for stable distros is fueled primarily by the growth of tools like flatpak. So, since linux users require an additional PM, the real question is: Are you using linux only for browsing and the occasional text editing?

    • lemmyvore@feddit.nl
      link
      fedilink
      English
      arrow-up
      2
      arrow-down
      1
      ·
      9 months ago

      Not to mention that the most common problems it solves can be solved by installing packages from source in a prefix like /opt or ~/.apps and symlinking them from a central place like /opt/.system or ~/.apps/.system or whatever.

      I had a bash script 15 years ago that automated most of this. (Which gradually fell out of use when Arch and makepkg came along, but I digress.)

      I can’t help but feel like nix is a solution looking for a problem and solving it in a way that appeals to a certain kind of hobbyist but not so much to any practical purposes. Otherwise it would have been adopted more widely by now.