• 0 Posts
  • 68 Comments
Joined 1 year ago
cake
Cake day: June 21st, 2023

help-circle










  • All of these points are completely correct and paint an accurate picture of the inherent issues with both technologies.

    My intent with my earlier comment was to show how flatpaks and appimages were different from traditional package managers at a high level so I could ask what made nixpkgs different from something I felt and still kinda feel is a more accurate comparison which are traditional package managers like apt etc.

    The big selling point to me now is that nixpkgs seem to work similarly to virtualenvs from Python which is cool.



  • toasteecup@lemmy.worldtoLinux@lemmy.mlWhy aren't more people using NixPKGs?
    link
    fedilink
    English
    arrow-up
    11
    arrow-down
    2
    ·
    9 months ago

    You’re not exactly comparing apples to apples here.

    Flatpak and appimages tend to be used in any distro because they can just be downloaded in a one off manner and installed then you’re running the application (for the most part). They offer a manager of sorts but you don’t need it to use the packages.

    For nixpkgs, whike I’m sure I can get a package from the sounds of the sizes the package covers only the application or the library, meaning I still need the dependencies.

    So what exactly would make me the user trade my built in tools (apt/pacman/dnf) for nix? Keep in mind no matter how great you feel it is, you need to provide reasoning that motivates me to install and learn this new tool instead of the old ones I have.