But yeah, Nix is much more than a homebrew replacement and that has its downsides.
1. Did't actually exist
2. Outdated version
3. Incorrect build
I'll keep the quality of Homebrew packages over the quantity in Nix
The 2/3 that are on nix are both out of date and created by some outside party.
I do not see a world where I provide nix stuff for my projects. There are already too many packages managers and I'm not spending my unpaid time to support all of them. GitHub and brew are my limit, def not learning nix just for this
@M4MBP ~ % brew list | wc -l
149
If the complaint is that other systems are less up-to-date than brew is, then the number of things installed is still the issue - whether they're dependencies or not.
Unless, of course, the other system manages dependencies differently, say it compiles in static versions of required libraries at build-time, or divides them up into fewer dependent packages.