3 ms·
> Although they seem to be more interested in keeping the bare minimum around versus making it easier for development, since there isn't a brew-esque thing buil
by skissane 7y ago
> Although they seem to be more interested in keeping the bare minimum around versus making it easier for development, since there isn't a brew-esque thing built in
I don't know anybody in the macOS development team, so I don't know their work practices, but it totally wouldn't surprise me if they've all installed Homebrew and use it heavily.
I infer Apple's attitude as being "if you are technical enough to use Homebrew, you are technical enough to download and install it yourself". (Or MacPorts, or Fink.)
If they bundle it... then people might start turning up at the Genius bar to complain "brew install X gives me an error!"
> my only major showstopper being that valgrind just straight up isn't a thing for recent versions of OS X, with the brew version not compiling on 10.15 or 10.14
I feel the same pain... I just use Docker for Mac to run valgrind for Linux. For my personal use cases, that works fine (since I don't write much macOS-specific code)
- yjftsjthsd-h 7y agoI thought macports was the quasi-official option; at least, it had Apple employees as founding members of the project. Granted, it's a bit sad that there's no Official package ecosystem, although I agree with you that support issues might be at play.
- saagarjha 7y agoMacPorts still has Apple employees on the core team, but it is no longer an official Apple project.
- saagarjha 7y agoMany of them don’t, actually: they just use the toolchain that Apple provides, and of course all scripts internally work with the old BSD tools so there’s really no need to install anything else unless you really like vim or GNU coreutils or whatever.
- throwaway5810 7y agoMany don't, but many do.
- saagarjha 7y agoYes, of course many do in fact enjoy using tools outside of Xcode and crusty shell scripts that someone else on the team wrote years ago :)