[lambdaba]

Yeah, I'm just addressing you specifically, you could switch easily and Nix has a much larger package selection (outside of GUI apps on macOS). And it immediately can do more via nix-shell -p, which can be also be used as shebang.

But yeah, Nix is much more than a homebrew replacement and that has its downsides.

[verdverm]

Nix may have a larger selection, but I sampled a few of the projects I install from homebrew and...

1. Did't actually exist

2. Outdated version

3. Incorrect build

I'll keep the quality of Homebrew packages over the quantity in Nix

[lambdaba]

I'm curious of what the packages are because I only have ~10 packages that I use from homebrew, either very Mac-specific or that have better packaging (ffmpeg, mpv)

[verdverm]

They are all projects that distribute Go binaries on GitHub and have official homebrew taps

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

[spacedcowboy]

Not going to list them all, but...

@M4MBP ~ % brew list | wc -l

149

[troupo]

Some/many of those are likely to be dependencies. For example, it shows openssl@1.1 and openssl@3 on my machine

[spacedcowboy]

Right, but I don't think that's the issue.

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.

[mbirth]

`brew leaves` will show manually installed packages.