8 ms·

>Really? What? * Conflicts with other software installed causing all sorts of weirdness. * Numerous packages not in the main repo that weirdly have to be inst

>Really? What? * Conflicts with other software installed causing all sorts of weirdness. * Numerous packages not in the main repo that weirdly have to be installed by some other mechanism (pip, cask, etc.). * Dependency on XCode. There's like a 5 step installation process to get it up and running! * brew install rsync -> rsync [xyz] -> why isn't this working? -> oh wait, the version of rsync on the PATH is still the ancient system one for some reason. * whatever brew doctor does. the fact that command even exists is a big red flag to me. ^^ This is just the stuff I've run into recently when I've had to debug stuff that was working just fine on linux but somehow broke on a somebody's mac.

OJFord 10y ago
> Conflicts with other software installed causing all > sorts of weirdness. Can't say I've had that, but I can imagine it happening - more of a `$PATH` issue than brew's fault though, surely. > Numerous packages not in the main repo that weirdly have > to be installed by some other mechanism (pip, cask, > etc.) There are 'taps' just like there's AUR, apt repos, et al. Cask is a tap away (and this is prompted if you try to run `brew cask <cmd>` without it), and pip is just `brew install python[version]`. > Dependency on XCode. There's like a 5 step installation > process to get it up and running! That is annoying, but you can condense it to a single command (`softwareupdate` piped to some nonsense) for a 'fresh install' script. I think the only way around this would be for brew to ship a compiled binary, and then mandate that you install either XCode Command-Line Tools, or gcc. (Some formulae will need to compile.) > brew install rsync -> rsync [xyz] -> why isn't this > working? -> oh wait, the version of rsync on the PATH is > still the ancient system one for some reason. Well that's just a broken `$PATH`. > whatever brew doctor does. the fact that command even > exists is a big red flag to me. It's a badly named debugging utility. It should just be `brew debug`. It even says when you run it: > Please note that these warnings are just used to help > the Homebrew maintainers with debugging if you file an > issue. If everything you use Homebrew for is working > fine: please don't worry and just ignore them. Thanks!
- crdoconnor 10y ago
  I'd just like to emphasize that: * This is basically just a cross section of problems I came across helping other people who used a Mac over the period of a few days. I can only imagine how bad it is using it day to day. * Everybody just accepted that these types of problems happened with a shrug. Except me because I've gotten used to them not existing (I almost never get PATH related issues on ubuntu). * They may all have a solution but they shouldn't exist in the first place. * They may not even be brew's fault per se, but it's still all part of the pain you have to deal with when using a mac which makes me want to toss it out the window.

OJFord 10y ago

> Conflicts with other software installed causing all > sorts of weirdness. Can't say I've had that, but I can imagine it happening - more of a `$PATH` issue than brew's fault though, surely. > Numerous packages not in the main repo that weirdly have > to be installed by some other mechanism (pip, cask, > etc.) There are 'taps' just like there's AUR, apt repos, et al. Cask is a tap away (and this is prompted if you try to run `brew cask <cmd>` without it), and pip is just `brew install python[version]`. > Dependency on XCode. There's like a 5 step installation > process to get it up and running! That is annoying, but you can condense it to a single command (`softwareupdate` piped to some nonsense) for a 'fresh install' script. I think the only way around this would be for brew to ship a compiled binary, and then mandate that you install either XCode Command-Line Tools, or gcc. (Some formulae will need to compile.) > brew install rsync -> rsync [xyz] -> why isn't this > working? -> oh wait, the version of rsync on the PATH is > still the ancient system one for some reason. Well that's just a broken `$PATH`. > whatever brew doctor does. the fact that command even > exists is a big red flag to me. It's a badly named debugging utility. It should just be `brew debug`. It even says when you run it: > Please note that these warnings are just used to help > the Homebrew maintainers with debugging if you file an > issue. If everything you use Homebrew for is working > fine: please don't worry and just ignore them. Thanks!

crdoconnor 10y ago
I'd just like to emphasize that: * This is basically just a cross section of problems I came across helping other people who used a Mac over the period of a few days. I can only imagine how bad it is using it day to day. * Everybody just accepted that these types of problems happened with a shrug. Except me because I've gotten used to them not existing (I almost never get PATH related issues on ubuntu). * They may all have a solution but they shouldn't exist in the first place. * They may not even be brew's fault per se, but it's still all part of the pain you have to deal with when using a mac which makes me want to toss it out the window.