Mitchell Hashimoto, creator of Ghostty terminal emulator and founder of HashiCorp, announced the project is leaving GitHub. In a detailed blog post, Hashimoto cites philosophical differences with Microsoft's direction for the platform and concerns about centralization. It's part of a trend that could crack GitHub's monopoly on open source hosting.
When Microsoft bought GitHub in 2018, developers worried about what would happen to the platform. Most stayed anyway because the network effects were too strong - everyone's code was already there, all the tooling integrated with it, and moving seemed like more trouble than it was worth. Now some of the most respected engineers in open source are reconsidering that calculation.
Hashimoto's reasoning is worth reading in full, but the core issue is control. GitHub's direction is increasingly tied to Microsoft's commercial interests. Features get prioritized based on enterprise sales potential, not community needs. The company that promised to be the neutral home for open source is becoming a Microsoft product with all that implies.
Copilot was the breaking point for many maintainers. GitHub trained an AI coding assistant on public repositories without meaningful consent from authors. Legally defensible under the licenses involved, but philosophically corrosive to the trust relationship that made GitHub the default choice for open source.
Where is Ghostty going? Probably Codeberg, GitLab, or self-hosted infrastructure. The technical migration is straightforward - git is distributed by design. The hard part is the ecosystem. GitHub Issues, Pull Requests, Actions, and all the integrations built around them don't transfer. Moving means rebuilding that infrastructure elsewhere.
But that's starting to feel worth it to developers who remember what open source culture looked like before Microsoft owned the infrastructure. The centralization of open source on a single corporate platform was always uncomfortable. It just took years for the discomfort to outweigh the convenience.
If Ghostty moves and other prominent projects follow, the network effects that kept everyone on GitHub start to reverse. Contributors will set up accounts on alternative platforms. Tool maintainers will add integrations. The ecosystem fragments, which is messy, but also resilient.
Monopolies persist until they don't. GitHub's dominance feels unshakeable because every developer you know uses it. But SourceForge felt unshakeable too before everyone moved to GitHub. Platforms die slowly and then all at once.
Hashimoto has enough credibility in the developer community that his decision carries weight. He's not some random maintainer rage-quitting over a policy change. He built tools that millions of developers use daily. When he says GitHub's direction is incompatible with his values, other maintainers pay attention.
Where your code lives matters. Who controls that infrastructure matters. For years, developers accepted Microsoft's stewardship because it mostly worked. But "mostly works" isn't the same as "aligns with community values." The gap between those two is where migrations begin.
GitHub won't collapse tomorrow. But if you're paying attention to where the most principled developers are moving their projects, you might want to consider whether the network effects that keep you there are weakening.
