The problem comes when you start wanting to use things that aren't on Macports, and are only on homebrew (or maybe fink). But homebrew won't work with macports! So either you have to install one package or the other manually, or you have to install both macports and homebrew, which means that not only are you dealing with an unsupported setup, but you're also dealing with using two separate package managers for the same operating system.
Oh, and don't forget that anything installed via the App Store is completely independent of all of the above.
As a Linux user, I find this concept mind-boggling. I don't have time to keep track of a thousand different package managers. I just want one that handles everything.
I'd say the opposite, forget about Homebrew and keep Macports.
The whole thing may not be so easy to use at first, but when you have read the docs for the port system, it all makes much more sense.
I've found that with Homebrew's very simple recipes, you can find one for pretty much anything. I've been satisfied with some binary vendor-provided packages + app store + homebrew for everything else.
I use the same solution as Miguel. Linux under VirtualBox. So in fact every Mac I've ever owned has also been a Linux machine too. In fact, sometimes several Linux machines!
The problem comes when you start wanting to use things that aren't on Macports, and are only on homebrew (or maybe fink). But homebrew won't work with macports! So either you have to install one package or the other manually, or you have to install both macports and homebrew, which means that not only are you dealing with an unsupported setup, but you're also dealing with using two separate package managers for the same operating system.
Oh, and don't forget that anything installed via the App Store is completely independent of all of the above.
As a Linux user, I find this concept mind-boggling. I don't have time to keep track of a thousand different package managers. I just want one that handles everything.