✳flâneur — a map of the web's best reading

Why GitHub Actually Won

blog.gitbutler.com · 4,610 words · saved by 6 readers

A few days ago, a video produced by @t3dotgg was posted to his very popular YouTube channel where he reviews an article written by the Graphite team titled “How GitHub replaced SourceForge as the dominant code hosting platform”. Theo’s title was a little more succinct, “Why GitHub Won”. Being a cofounder of GitHub, I found Greg’s article and Theo’s subsequent commentary fun, but figured that it might be interesting to write up my own take on the reasoning behind the rise and dominance of GitHub and perhaps correct a few things that were not quite right from their outside analysis. Being at the very center of phenomena like this can certainly leave you with blind spots, but unlike these youngsters, I was actually there. Hell, I wrote the book. So here’s an insider’s take on why GitHub won. If you want a very short read, here is the quick version of why I believe GitHub won and why you’re probably using the site to this day. I can boil it down to exactly two reasons that happened to res

Why GitHub Actually Won | Butler's Log 1 year ago by Scott Chacon 19 min read Why GitHub Actually Won How GitHub _actually_ became the dominant force it is today, from one of it's cofounders. A few days ago, a video produced by @t3dotgg was posted to his very popular YouTube channel where he reviews an article written by the Graphite team titled “ How GitHub replaced SourceForge as the dominant code hosting platform ”. Theo’s title was a little more succinct, “ Why GitHub Won ”. Being a cofounder of GitHub , I found Greg’s article and Theo’s subsequent commentary fun, but figured that it might

Explore this link on the map →

saved by

related reading