4 ms·
Homebrew starts from the MacOS CLI apps provided through XCode. It's a usermode package manager built on top of XCode components. MacPorts builds everything f
by jdonaldson 6y ago
Homebrew starts from the MacOS CLI apps provided through XCode. It's a usermode package manager built on top of XCode components. MacPorts builds everything from scratch, which grants more power and optimization opportunities, but comes with many, many more rough configuration edges to deal with.
The optimization opportunities for some packages are typically on the order of 2x-5x faster, which isn't enough to deal with the headache of extra config for a personal dev box. So, my rule of thumb is, unless I know exactly the performance trade off I am trying to take advantage of by going with MacPorts, I will be better served by using Homebrew. I will wind up spending more time fixing config then I will have saved on execution processing time.
- anaerobicover 6y ago> Homebrew starts from the MacOS CLI apps provided through XCode As does MacPorts. https://guide.macports.org/#installing.xcode https://guide.macports.org/#installing.xcode > MacPorts builds everything from scratch This has not been true for many years: https://trac.macports.org/wiki/FAQ#fromsource https://trac.macports.org/wiki/FAQ#fromsource
- Isthatablackgsd 6y ago> As does MacPorts. https://guide.macports.org/#installing.xcode https://guide.macports.org/#installing.xcode For some reason, It is PITA to get MacPorts to recognize Xcode. It took me three days to get MacPorts to see it. I tried various configuration, arguments, versions, etc until it's finally working.