Ghostty's GitHub Exit: Finally, Someone Said It Out Loud

Rating: 9/10 - This matters more than you think.

Look, Mitchell Hashimoto just did what every serious open-source maintainer has been thinking but too afraid to say publicly: GitHub has become a chokepoint, and it's not sustainable. This isn't nostalgia. This is a fundamental power dynamics problem wearing a friendly UI.

The real story here isn't that Ghostty is leaving—it's that a founder with actual leverage and credibility is willing to take the friction hit of migration to prove a point. Hashimoto built Vagrant, Terraform, and Consul. He's not some random dev venting on Twitter. When someone at that level says "centralization risk," institutional investors should be taking notes.

GitHub's monopoly has been baked in so long we forgot to question it. Microsoft owns it. They can change terms, pricing, or policies whenever they want. They can shadow-ban your project. They control the narrative around what gets recommended. And most developers just... accept it because the switching costs feel too high. Ghostty proves they're not actually that high for determined teams.

The business opportunity here is real but narrow: alternative Git platforms won't win by being "Git but decentralized." They'll win by being boring, reliable, and cheaper. Gitea, Forgejo, and Codeberg are already here. The exodus will be slow, incremental, and unglamorous—but inevitable for maintainers who care about long-term independence.

The uncomfortable truth? Most developers won't follow. Path dependency is a hell of a drug. But the fact that the best projects can leave? That changes everything about GitHub's actual negotiating position.

Signal strength: High. This is the opening move of a longer transition.

Stay sharp. — Max Signal