GitHub's Fight for Survival Under Microsoft
Nearly eight years after Microsoft acquired GitHub for $7.5 billion, the platform is battling for its survival. A surge of outages, security vulnerabilities, and a mass exodus of talent have left GitHub struggling. In recent weeks alone, GitHub experienced multiple major outages, a remote code execution vulnerability, and a breach of its internal code repositories due to a malicious VS Code extension. Current and former employees describe a company grappling with a lack of leadership and mounting pressure from competitors like Cursor and Claude Code.
Leadership Void and Talent Drain
GitHub's troubles trace back to last summer when former CEO Thomas Dohmke resigned. Microsoft did not replace him, forcing GitHub's leadership to report directly to Microsoft's CoreAI team, led by former Meta engineering chief Jay Parikh. Parikh is reportedly unpopular among Microsoft employees, and his decision not to appoint a new GitHub CEO has sparked a talent drain. Many Hubbers have followed Dohmke to his startup, Entire, a direct competitor. Out of 30 employees at Entire, at least 11 previously worked at GitHub.
Competition Heats Up
Parikh has privately warned colleagues that GitHub faces a critical threat from Cursor and Claude Code. GitHub Copilot, once a leader in AI coding tools, has fallen behind rivals. Microsoft even considered acquiring Cursor to close the gap. Meanwhile, Microsoft is canceling Claude Code licenses to push developers toward improving GitHub Copilot.
Key Departures Shake GitHub
Veteran Microsoft executive Julia Liuson departed after 34 years. Jared Palmer, a senior vice president who joined GitHub in October, is leaving for Xbox. Elizabeth Pemmerl, GitHub's former chief revenue officer, also resigned. With revenue now reporting into Microsoft's MCAPS division and product work split into Developer Division, insiders feel GitHub's leadership has vanished. One employee lamented, "There's basically no more GitHub at all anymore. It's all Microsoft, and the company is collapsing."
Outages and Security Breaches Erode Trust
GitHub's outages have worsened over the past year, forcing CTO Vladimir Fedorov to apologize personally. He cited a growth spike in pull requests, commits, and new repos. The platform's migration to Azure servers, complicated by MySQL clusters, has contributed to instability. Developers like Ghostty terminal creator Mitchell Hashimoto are leaving, stating, "GitHub is failing me every single day. I can't code with GitHub anymore."
Security Vulnerabilities Mount
GitHub rushed to fix a critical vulnerability in its internal git infrastructure in March, which could have exposed millions of repositories. Earlier this week, 3,800 internal repositories were breached after an employee installed a malicious VS Code extension. Microsoft employees note that VS Code extensions with high install counts have previously been compromised with cryptomining tools.
Usage-Based Billing Backlash
GitHub faces backlash over its move to usage-based billing for GitHub Copilot. Starting next month, plans will include a monthly credit allotment, with users cut off unless they purchase more. Developers previously enjoyed unlimited experimentation, but now face limits.
The Future of GitHub Hangs in the Balance
Pressure mounts on Parikh and the CoreAI team. Competitors race to build the next GitHub, capitalizing on Microsoft's struggles. If Microsoft's CoreAI team cannot stabilize GitHub, the company risks losing the developers who helped make it a software giant. The survival of GitHub depends on restoring trust, fixing outages, and retaining talent.
The Pad: Microsoft Retires Together Mode
Microsoft is retiring Teams' Together Mode, a pandemic-era feature that simulated shared conference rooms. As businesses return to offices, Microsoft shifts focus to more streamlined collaboration tools.
Comment