I can think of several possibilities (not exclusive): - Mac users switching to or using linux, so no familiarity with other package managers to lead them elsew

I can think of several possibilities (not exclusive): - Mac users switching to or using linux, so no familiarity with other package managers to lead them elsewhere. - Packages are easy to create with their ruby DSL; it might appear gimmicky but it's very easy to pick up despite possibly being less robust? The command `brew create <tar file url>` even creates a template for you. - CLI is super easy to use; `brew info <package>` tells you everything you need to know; not a significant advantage for anyone willing to read a man page. - Existing packages as you said, plus it's still a hip package manager so... following contributions is easy? (Again, not a significant advantage except maybe for beginners.) Most likely: the people who are already familiar with it want to use it elsewhere (their VMs, dual-boot setup, servers, ...). Edit: Plus whatever is "unique" to brew / what totalrobe listed.