4 ms·
To be absolutely clear: what Homebrew is doing here is consistent with what every other system package manager does. If you've ever done `do-release-upgrade` to
by woodruffw 6y ago
To be absolutely clear: what Homebrew is doing here is consistent with what every other system package manager does. If you've ever done `do-release-upgrade` to bump your Ubuntu LTS, you'll have run into the exact same problem.
The only difference is that Homebrew doesn't have a stable system distribution to pin to (we're not Apple, and we have no say over macOS's development), so we make upgrade decisions for packages like Python based on their stability with our packaged ecosystem. It's a poor practice to use your system Python distribution for any sort of virtualized development environment, and Homebrew behaves identically to every other system package manager in that regard.
Please keep in mind that we're a community of volunteers answering to millions of users. Your idea of "user hostile" is our idea of "simple for the sake of preserving our sanity."
- CamJN 6y agoNo other package manager I've used automatically performs destructive actions on a package installation without asking me, homebrew does. But aside from that, homebrew used to be much nicer, it had options on formulae, it worked with the system ruby instead of installing its own periodically, it allowed patches that improved system integration even if they made the resulting binary less command line focused (for example emacs has macOS specific patches locked behind building the gui app). And yeah, it's the homebrew maintainer's project, but when you're in a position to help people or make their life worse, it's immoral to do the latter.