11–20 of 22 posts
Brew is just fine as it is, unless you’re running an older version of macOS and it has to build packages from source.
For someone whose needs are generally met with homebrew, what are its major issues (aside from speed)?
- In practice, requires being installed to /usr/local
- Hard to uninstall in practice, leaves files scattered behind
Nix
99% of the time I spend running “brew” is downloading time, so I honestly don’t get this question. What kind of Internet connection do you have? Brew is just fine as it is, unless you’re running an older version of macOS and it has to build packages from source.
99% of the time I spend running “brew” is downloading time, so I honestly don’t get this question. What kind of Internet connection do you have? Brew is just fine as it is, unless you’re running an older version of macOS and it has to build packages from source.
When I used to use brew, most of the time was brew doing housekeeping. You could see the title bar change processes twenty times a second, often ruby, as it did whatever it was doing, even for simple commands like search or before upgrade confirmation is approved.
export HOMEBREW_NO_INSTALL_CLEANUP=1
Nix
(used to be that you could just `brew install https://link/to/git/commit` which they disabled for "security reasons", the replacement is that you need to make your own tap which is quite a bit more effort)
For someone whose needs are generally met with homebrew, what are its major issues (aside from speed)?
- Doesn't allow installing multiple versions of packages at the same time - In practice, requires being installed to /usr/local - Hard to uninstall in practice, leaves files scattered behind