Homebrew is downright dangerous (I've written about why: http://inthebox.webmin.com/homebrew-package-installation-for... ).
MacPorts is fine. Not wonderful, but OK. Not reproducible in the way Nix is.
PkgSrc is also pretty good. Also not reproducible the way Nix is. But, the packaging policies are good, the packages tend to be well-thought out, and the technical solution to stuff like dependency resolution is pretty OK. The people building and maintaining PkgSrc know what they're doing.
Nix is clearly superior to all of them, however, in being reproducible, easy to roll-back in a predictable way (try going backward with almost any other package manager, even RPM/yum and dpkg/apt can't do that...I love'em both, but recognize that we now have better solutions to package management). Nix is just a fundamentally better tool.
Flatpak is another really promising packaging technology with some of the same benefits (but it's tackling things in a different way; I think I still have to consider Nix a better overall solution; it is certainly simpler in both implementation and usage, for packagers/developers and end users).
But, don't use Homebrew. For now, PkgSrc is probably the best method of getting a lot of reasonably good packages for Mac OS X. Nix will be the better option eventually, once there's a lot of people packaging for it (assuming people get over their bizarre love affair with Homebrew and start working with Nix, instead).
Your link specifically covers the case of Homebrew on the server. But Homebrew isn't meant to be a server package manager. It's an OS X package manager, and OS X is a desktop operating system, not something that most people choose to use as a server (OS X Server exists but is primarily used for intranet stuff rather than as a production server). The complaints that your link has are only problems for an external-facing server. They're not problems for desktop use. And the simple answer to that is: don't use a desktop package manager on your server.
The wording dangerous was poorly used, inappropriate for server package management would have been better.
So, yes, to be clear: The dangers of Homebrew are primarily when considering it for use in a server context. I personally wouldn't use it anywhere. But, it has many good qualities that many people value highly.
If you want to say "Homebrew is dangerous when used on a public-facing server", that's entirely fair. But that's not what you said. I'm glad that you do recognize this distinction though, and I hope you will think twice before claiming again that Homebrew is dangerous without qualification.
Install emacs with brew Install spacemacs on top of emacs It works!
To pull users from brew it needs to work at least as well, especially for common tools like emacs. Go check out the number of issues related just to emacs installs, it is kind of amazing.
Just about everything else I'd like to use is packaged, so Id like to think we're over the adoption-pkg-count chicken egg problem.
$ pkgin se python3
python35-3.5.1nb2 Interpreted, interactive, object-oriented programming language
python34-3.4.4 Interpreted, interactive, object-oriented programming language
python33-3.3.6nb3 Interpreted, interactive, object-oriented programming language
along with a bunch of pre-packaged modules: $ pkgin avail | grep ^py3 | wc -l
1412
Let me know if anything you need is missing and I'll add it.I have just found a related issue: https://github.com/joyent/pkgsrc/issues/331 Unfortunately, from what I read there, I have still to use homebrew or install from python.org (with those I have no issue). I really enjoyed pkgin otherwise.
apt-cache search
aptitude isn't necessarily installed.The new apt, if you have it, now combines apt-get with apt-cache plus a bunch of UI improvements.
apt search ...
apt install ...
If you've got it, it's well worth a look.
I'm looking forward to future posts that show how Nix is better than Homebrew or MacPorts, because that hasn't been demonstrated so far.
And as a bikeshed nitpick, I was always unhappy with the meaningless rpm options, preferring apt's clearer options (rpm -qa vs aptitude search). I'm a bit disappointed that nix chose to mimic rpm's style. Oh well, tomayto/tomahto.