Welcome to my Linux distro showdown! I'll rank Linux distributions based on my personal experience and factors like stability, package manager, community support, privacy/security, & customizat...
Rollbacks are definitely something worth talking about, but the package count is probably not.
Nixpkgs automatically generated packages from some language specific package managers, mainly Haskell and Node packages, which do hugely inflate the number. If you account for these, it does end up being smaller than the AUR. Plus, many of those automatically generated packages are frequently broken.
This still leaves Nixpkgs as the largest official repo, but I think any NixOS maintainer would agree that the average quality of a package in NixOS is not as high as something like an official Arch or Debian package. Package review processes are not nearly as intensive as they probably should be due to the lack of manpower to handle that…
Edit: To be clear, since my tone seemed very negative here, I am not just trying to spread negativity about NixOS. I’ve used NixOS for years and contributed to plenty of Nix projects in the time. It is without a doubt the best package manager atm and its ideas have had massive positive impacts on package management as a whole.
I think any NixOS maintainer would agree that the average quality of a package in NixOS is not as high as something like an official Arch or Debian package
Package maintainer here. Not sure what you mean by quality; as that term is very ambiguous. Shit works and configuration is often a breeze by comparison to other distros.
I would never go back to a legacy distro. Who wants to do that shit all by hand?
I didn’t say or imply that NixOS is worse than other distros overall. I am also a maintainer of several packages, but I am referring to those with Nixpkgs write access, who generally have a deeper understanding of the repo.
Shit usually works, but not always. Breakages on unstable are not uncommon. For example, things often break when a major Python package is updated. The auto generated packages in Nixpkgs are often broken, sometimes completely, but sometimes in ways you don’t realize until you’re using them. Nixpkgs just does not have a review process that is on par with other distros.
I agree that NixOS configuration is amazing, that’s not what I was talking about. Im not shit talking NixOS, I love Nix and have used and contributed to it for years. I’m just bringing up valid points about it that are worth talking about.
Nixpkgs just does not have a review process that is on par with other distros.
We can agree on this. There is work to do.
Breakages on unstable are not uncommon.
I run unstable, and I have had this happen twice. Both times with Tmux (which is weird); but it was upstream issues. But fair enough. Maybe my systems aren’t exotic enough to experience the uncommon breakages.
Could nixpkgs do better? Yes. I mean, look at the backlog. You have to be active in the community to get your work merged in any decent timeframe. I think this is the most annoying part about the Nix ecosystem.
Maybe my systems aren’t exotic enough to experience the uncommon breakages.
The majority of issues are caused by Python applications, because Python packaging in Nix is still very rough. This isn’t Nix’s fault though, its the fact that pip sucks and most Python software uses a simple requirements.txt. Hopefully one day Poetry and UV build helpers will be in Nixpkgs.
You have to be active in the community to get your work merged in any decent timeframe. I think this is the most annoying part about the Nix ecosystem.
Definitely agree. It can be hard to get things merged or even reviewed. The simplest option to improve this would be to give more people write access, but of course lowering requirements for getting it would be a risk for security and stability. Nixpkgs automation is frequently improving, which will definitely help.
Rollbacks are definitely something worth talking about, but the package count is probably not.
Nixpkgs automatically generated packages from some language specific package managers, mainly Haskell and Node packages, which do hugely inflate the number. If you account for these, it does end up being smaller than the AUR. Plus, many of those automatically generated packages are frequently broken.
This still leaves Nixpkgs as the largest official repo, but I think any NixOS maintainer would agree that the average quality of a package in NixOS is not as high as something like an official Arch or Debian package. Package review processes are not nearly as intensive as they probably should be due to the lack of manpower to handle that…
Edit: To be clear, since my tone seemed very negative here, I am not just trying to spread negativity about NixOS. I’ve used NixOS for years and contributed to plenty of Nix projects in the time. It is without a doubt the best package manager atm and its ideas have had massive positive impacts on package management as a whole.
Again, just subtract all the unique packages and you still get more packages than the AUR
If other distros have the same package, it’s not a machine generated package, is it?
Package maintainer here. Not sure what you mean by quality; as that term is very ambiguous. Shit works and configuration is often a breeze by comparison to other distros.
I would never go back to a legacy distro. Who wants to do that shit all by hand?
I didn’t say or imply that NixOS is worse than other distros overall. I am also a maintainer of several packages, but I am referring to those with Nixpkgs write access, who generally have a deeper understanding of the repo.
Shit usually works, but not always. Breakages on unstable are not uncommon. For example, things often break when a major Python package is updated. The auto generated packages in Nixpkgs are often broken, sometimes completely, but sometimes in ways you don’t realize until you’re using them. Nixpkgs just does not have a review process that is on par with other distros.
I agree that NixOS configuration is amazing, that’s not what I was talking about. Im not shit talking NixOS, I love Nix and have used and contributed to it for years. I’m just bringing up valid points about it that are worth talking about.
We can agree on this. There is work to do.
I run unstable, and I have had this happen twice. Both times with Tmux (which is weird); but it was upstream issues. But fair enough. Maybe my systems aren’t exotic enough to experience the uncommon breakages.
Could nixpkgs do better? Yes. I mean, look at the backlog. You have to be active in the community to get your work merged in any decent timeframe. I think this is the most annoying part about the Nix ecosystem.
The majority of issues are caused by Python applications, because Python packaging in Nix is still very rough. This isn’t Nix’s fault though, its the fact that pip sucks and most Python software uses a simple requirements.txt. Hopefully one day Poetry and UV build helpers will be in Nixpkgs.
Definitely agree. It can be hard to get things merged or even reviewed. The simplest option to improve this would be to give more people write access, but of course lowering requirements for getting it would be a risk for security and stability. Nixpkgs automation is frequently improving, which will definitely help.