Bootstrap creators leave Twitter for Obvious and GitHub but vow to keep working on open-source project
Mark Otto and Jacob Thornton (aka @mdo and @fat), who jointly cooked up front-end Web app development toolkit Bootstrap whilst working at Twitter, have decided to leave the social networking company after 2.5 years.
Context & Ripple Effects
Bootstrap began as an internal Twitter tool before its public release in August 2011 (Bootstrap from Twitter), and has since become one of the most widely adopted front-end toolkits on the web. Its two creators, Mark Otto and Jacob Thornton, are now leaving the company that incubated it — Otto to Obvious, Thornton to GitHub, which itself just raised a $100M Series A in July 2012 (GitHub's $100M Series A).
The departures land at a delicate moment for Twitter's developer relations: less than two weeks earlier, developers were openly angry about API access limits while CEO Dick Costolo was telling Charlie Rose the company is building a 'true platform.' The pair's vow to keep Bootstrap alive outside Twitter tests whether a project can survive detaching from its corporate sponsor — a question StockTwits was already probing by building out its own ecosystem independent of Twitter.
First-order effects
- Twitter loses the two engineers who built and championed Bootstrap, meaning the toolkit's roadmap now runs entirely outside the company even as Twitter's own web properties presumably still depend on it.
- Thornton lands at GitHub weeks after its $100M round, giving GitHub an in-house stake in one of open-source front-end development's flagship projects.
Second-order effects
- GitHub strengthens its pull as the default home for high-profile open-source maintainers, while Obvious — the company behind Blogger and Twitter itself — adds another creator with a track record of building widely used publishing tools.
- Companies that adopted Bootstrap because 'Twitter made it' must now evaluate it as an independently governed project, shifting trust from a brand to the maintainer community around the repository.
Third-order effects
- If Bootstrap thrives post-Twitter, it becomes a template for internal tools escaping their corporate birthplaces — companies may increasingly treat open-sourced infrastructure as portable assets rather than proprietary differentiation.
- The episode feeds a broader strain between Twitter and its developer ecosystem, where API restrictions and departing builders push third-party developers toward platforms and projects less subject to a single host's product pivots.
The trend: Open-source projects born inside large platforms are becoming portable assets whose maintainers can carry them to new employers, decoupling popular developer tools from the companies that created them.