legacy-homebrew

ch would be nice... half the time I have better luck searching their issues via Google than using Github's own search tool[2]). 6) A responsive web front-end. The reason that they use Github's built-in issue tracker in the first place is because everyone and their mother has a Github account, so it lowers the barriers to entry for filing a bug report. And there's no question that they've benefited enormously from this, and the user-engagement that it enables. But the detriments to productivity are real, and the advantage of Github's network effect hasn't stopped them from repeatedly considering migrating their issues to Bugzilla. And I don't think it would kill Github to abandon their "tags fulfill EVERY USE CASE" position and bake in some more features for advanced users, especially if they hope to capture a bigger share of the more "serious"[2] projects out there (which would only be to their benefit, considering that "serious" projects are the ones that are willing to buy paid accounts for all the users in their organization). [1] "Large" in this case meaning: hundreds of Github forks, thousands of Github stars, hundreds of thousands of lines of code, a half-dozen full-time developers, and, most pertinently, several thousand issues (and growing at an increasing rate). [2] Case in point: I just now tried to search for the issue wherein I offered to do the legwork of migrating their database to Bugzilla should it come to that. The title of the issue contains the word "Bugzilla". The text of the issue itself contains the word "Bugzilla" multiple times. Several of the comments contain "Bugzilla". And yet a search for "Bugzilla" using Github's issue search tool reveals only one issue, completely unrelated to the issue I was looking for. [3] "Serious" in this case meaning: a codebase with hundreds of thousands to millions of users, dozens of full-time developers, and hundreds of thousands of issues.[4] [4] https://bugzilla.mozilla.org/show_bug.cgi?id=800000 [5] [5] Help I've gone mad with footnote power [5] [6] While you're here, fun fact: I once went looking for the Github project with the largest number of total issues, and here's what I eventually settled upon: https://github.com/mxcl/homebrew/issues

g your own formula is easy if manual steps are easy, and if they're hard, well, writing a formula makes you do it only once, since you'll be able to reuse the formula later. Anyway brew builds in Cellar, and symlinks in /usr/local but never steps on what you would have installed manually.

arn keyboard shortcuts by heart (press down CMD key for 2 seconds to get a list of all shortcuts) - Check this blog out - it has plenty of great stuff about OS X that even veteran OS X users don't know (trust me, I know a lot of them): http://www.macyourself.com - You'll inevitably wonder what 'ocspd' or 'mdworker' are, when using 'ps -Ac' or 'top' (spoiler: ocspd is for certifications, and mdworker, or metadata-worker is a process that gathers information about files and feeds them to Spotlight for search), so install atMonitor (http://www.atpurpose.com/atMonitor/) instead of searching for process names on the Internet. It offers tons of other cool features. - Markdown Pro (http://www.markdownpro.com) and Mou (http://mouapp.com) for Markdown. - As much as I despise iTunes, nothing comes close to it (unfortunately) in terms of media management. - Bartender - tidies messy menu bars: http://www.macbartender.com

fited me with respect to getting down with the nitty gritty of it and not complaining it was different to my Notepad++ experience prior on Windows.

th a lot of files in it (such as the definition files for Homebrew, which I'm occasionally in a position where I need something quickly verified or checked) you are pretty much screwed (and on MobileSafari I've had the browser run out of memory and simply crash). The result is that it is infinitely easier to just check the code out and edit it locally (yes: even and especially so on an iPhone, where git itself works great). In addition to having clicking through the code be reasonably fast, you have much more powerful search operations available. (edit:) Back at my laptop (aforementioned Air with Chrome), and to demonstrate part of the problem: go to the Formula folder for Homebrew, click any file, and then hit back. This takes multiple seconds to occur: hitting back is something that you are going to do constantly while browsing files, and is something that normally is instantaneous. https://github.com/mxcl/homebrew/tree/master/Library/Formula The reason for this is that the mechanism GitHub is using to supposedly speed up browsing (and I take severe issue with this: the surrounding content and resources should entirely be in the request cache, and there is almost no dynamic content on the page, so there should be more intelligent ways of improving the performance for clicking forward that are server-side) totally ruins the page cache. To be clear: the page cache is not the same as the request cache. The page cache is what is used when the user hits back or forward, and it stores all of the state associated with a rendered page. This way, when you click a link, you don't destroy all of that work, and when you hit back you get the previous contents as fast as possible. http://www.webkit.org/blog/427/webkit-page-cache-i-the-basic... (Note: this page states that pages that use HTTPS, such as apparently all of GitHub, are not able to be stored in the page cache. However, this was only true of WebKit, not Firefox's equivalent cache, and this was changed recently to bring the behavior in line: only if the page has Cache-Control: no-{store,cache} will the page be kept from the page cache.) http://trac.webkit.org/changeset/107607