4 ms·
<cries in MacPorts>
by AceJohnny2 2y ago
<cries in MacPorts>
- TMWNN 2y agoI also use MacPorts, but certainly have often noticed that Homebrew has some package that MacPorts doesn't. I guess there's nothing stopping me from moving to Homebrew other than familiarity.
- fastball 2y agoI used MacPorts a decade ago, but at some point realized that Homebrew had more packages that were kept consistently up-to-date. Switched and never looked back.
- nicolas_t 2y agoI switched away back to macports when homebrew decided to get rid of formula options. To be honest, I always find homebrew frustrating, it feels that they've often made technical decisions that are not necessarily the best but they've been much more successful at marketing themselves than macports.
- pnw_throwaway 2y agoIf I’m reading the formula docs right, only homebrew-core packages don’t support it (due to CI not testing them). That part does suck, though. Other taps, like homebrew-ffmpeg, offer a ton of options.
- nicolas_t 2y agooh, I actually hadn't realized that this is what they settled on in the end. ffmpeg is the quintessential package where options make sense so good that that's still supported. The other issue I experienced with homebrew around that time were related to having different versions of openssl installed because I had some old codebase I had to run (and for performance reasons didn't want to use docker). But that's definitely a edge case.
- detourdog 2y agoI haven't looked at Homebrew since that got started. The philosophical difference at that time was using macports and having a consistent and managed */local/ collection of tools with self contained dependencies vs. adding new tools with dependencies tied to the current Mac OS release. I still use MacPorts for that reason and it is easy enough to create a local portfile for whatever isn't in Macports. I find this to be the easy way to manage networked development computers.