<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">On Mar 12, 2014, at 2:12 PM, Art McGee <<a href="mailto:amcgee@gmail.com">amcgee@gmail.com</a>> wrote:<br><div><br class="Apple-interchange-newline"><blockquote type="cite"><span style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;">The problem is that the presentation of the case for supporting MacPorts was confusing and unconvincing, so usage statistics are not going to help in that matter.</span><br style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"></blockquote></div><br><div>I’ve been wondering why Homebrew has such huge momentum and mindshare these days. In random places on the web I’ve seen people imply that it’s better/more reliable than Macports. (The only concrete example was terribly outdated, about TexLive version about four years ago.) </div><div><br></div><div>I’ve given Homebrew a quick try in a VM and it doesn’t seem that different in functionality. (Except that I do wish we had something like Homebrew-cask.) So, other than the coolness factor (which I guess comes partly from being “the new thing”, and partly from using Github for all development and distribution), what else is there? Try to keep it factual and based on your own experiences using/administering both, please.</div><div><br></div><div>Davor</div></body></html>