← Acquired

GitHub

第2018-06-06期2018-06-06English会员内容
GitHub
收听本集00:00 / 1:22:19
阅读设置
按你的习惯阅读
正文字号
下载播客精读
把这一篇,带走慢慢读

英文 · 精读 · 当前版本

下载功能还未开放

正文语言

精读 · 按主题梳理核心观点、论证与案例。

§01Why GitHub Became the Social Layer of Software Development

The episode opens immediately after Microsoft announced its $7.5 billion acquisition of GitHub. The hosts frame the deal as a meeting between a San Francisco developer platform and a Seattle technology company, then explain that understanding the price requires two kinds of context: how software projects are managed and how the open-source ecosystem evolved.

Software configuration management developed from a single shared machine, to centralized client-server repositories, and finally to distributed version control. Centralized systems made one repository canonical but made private experiments, long-running forks, and contributions from distributed developers awkward. BitKeeper helped manage Linux development in the late 1990s, but when its company withdrew the free license in 2005, the open-source community produced Mercurial and Git. Git, created by Linus Torvalds and quickly adopted by projects such as Linux and Hadoop, managed versions but did not itself provide a social place to host and discuss code.

The remaining gap was filled by code forges such as SourceForge and Google Code, but these mainly hosted files and basic project pages. The hosts describe a shift toward consumer social networks and ask what would happen if developer discussion, collaboration, and code hosting lived together. Tom Preston-Werner’s Grit project became the starting point: after an encounter with Chris Wanstrath at a Ruby on Rails meetup, the two began building a web interface for distributed Git repositories. They worked nights and weekends, used the product inside Chris and PJ Hyett’s startup, and launched GitHub in January 2008. Its immediate product-market fit created rapid adoption and also exposed the founders to substantial hosting costs.

好对话,值得读完整。

免费试读到此结束。开通书架会员,继续阅读全文,解锁中英对照与电子书下载。