3 ms·
antonovka had some interesting comments on why macports does the things it does when homebrew was doing the rounds a few months back: http://news.ycombinator.c
by tvon 17y ago
antonovka had some interesting comments on why macports does the things it does when homebrew was doing the rounds a few months back:
http://news.ycombinator.com/item?id=872072 http://news.ycombinator.com/item?id=872072
It's worth a quick read, imo.
- jokull 17y agoThat is indeed a good read. Maybe MacPorts needs a better website where they explain this stuff. You gotta give it to Homebrew - the one page README is better then the "MacPorts Official Homepage" front page. (In fact, GitHub's one-page-README-intro is a terrific example of restraint producing better results). I still like the git-recipe idea. Perhaps MacPorts should have a Git repository of 'rouge' community ports they can periodically review for merging and then inclusion.
- tvon 17y agoI think Rails (or 37signals) taught developers that a little marketing savvy isn't a bad thing, and that thinking has in turn permeated the ruby community and shows itself in projects like Homebrew. Not smarmy marketing, it's just hackers asking themselves "how can I most simply show how powerful this is", more or less.