Brew is the single thing that I absolutely loathe about macOS.
It dog slow (does it really need to git pull from GitHub every 15 minutes, really?), doesn't support multiple users, doesn't support alternative folders, hates static compilation (which is mostly why the two previous break), and lots of new things are not available there anymore.
In my new computer I didn't even install it, I just used the Rustup/Dotnet/RVM/NVM install instructions rather than using Brew. I then got statically compiled versions of ffmpeg, jq, z7, which took a couple minutes. Let's see how long until I cave. I'll probably try MacPorts.
I've been slowly transitioning to using nix for all my software installations on macOS: it's pretty nice to have one tool that can manage all my 3rd-party software; manage the configuration of a bunch of programs, via home-manager; and, with lorri and direnv, replace nvm/rbenv/etc.
There were multiple successful package manager systems on macOS (MacPorts and fink) before brew came out. Brew hardly has any technical advantages over them except that maybe fink got stuck using an older version of dpkg/apt, and it made some new mistakes like installing in /usr/local.
Instead what seemed to happen is a new generation of Rails developers got Macs, decided all their tools needed to be written in Ruby by hipsters with lumberjack beards, and so they didn't want to touch the old stuff.
Yes. Brew is a crutch, and so network hungry. Nobody cares, but if you move to the mountains and want to do software development, a Mac will grind to a halt every so often for myriad reasons decided by someone at Apple, or just some dev accustomed to 100mbps.
Linux (Arch for me, but probably others) can be told to respect your personal situation, as opposed to dictating it.
ArchLinux has been painless. although I must say I've not tried anything too cutting edge with the GUI. Even if you don't use Arch, the Wiki is invaluable.
The wiki... Shows that community maintained resources don't have to suck.
I'm just using Sway and yay all day. The blunt edge works for me.
And, can't say this enough, please always keep in mind that your software may be used by someone with a slower connection or who may even be entirely offline sometimes. I deserve music while driving, and text is king. (Elon - starlink me please)
Both of these experiences are completely unlike mine, but I guess that goes to the variances in what people want and use.
The one thing I want in brew and don't have, is hugin. Nothing else I use is missing. Iterm and docker and other cask like installs can be ropey especially if they do update checks inside themselves.
I, probably a very simplistic user compared to others. YMMV.
I've been using MacPorts continuously for about 10 years now. It's been completely pain free. I think I ran into a single broken package in that time period.
> I just used the Rustup/Dotnet/RVM/NVM install instructions rather than using Brew. I then got statically compiled versions of ffmpeg, jq, z7, which took a couple minutes.
This is the setup I prefer in a vacuum, although it depends on the stuff you need being available.
I also do think MacPorts is quite good. It follows UNIX principles, and it doesn't try to take over the systems. Everything is contained in its own world inside /opt/.
It dog slow (does it really need to git pull from GitHub every 15 minutes, really?), doesn't support multiple users, doesn't support alternative folders, hates static compilation (which is mostly why the two previous break), and lots of new things are not available there anymore.
In my new computer I didn't even install it, I just used the Rustup/Dotnet/RVM/NVM install instructions rather than using Brew. I then got statically compiled versions of ffmpeg, jq, z7, which took a couple minutes. Let's see how long until I cave. I'll probably try MacPorts.