Microsoft's bad obsession is showing up in shabby services and slipshod software. Here's proof
Microsoft is facing criticism for declining service quality across its platforms, particularly GitHub, which has suffered from frequent outages and reliability issues. The company's aggressive integration of AI features, such as those in GitHub, has led to user dissatisfaction and the need for usage rationing. Once a trusted industry standard, GitHub's instability under Microsoft's stewardship raises concerns about its role as a critical resource for developers and open-source collaboration.
- ▪GitHub has experienced daily outages, leading prominent developer Mitchell Hashimoto to question its reliability for production use.
- ▪Microsoft's push to integrate AI into GitHub has resulted in unsustainable demand and the introduction of usage limits.
- ▪GitHub serves as a vital educational resource and industry standard for source control, collaboration, and open-source project management.
- ▪The article argues that Microsoft has failed to uphold the responsibility that came with acquiring GitHub, despite initially preserving its independence.
- ▪Windows 11 has increasingly steered users toward paid Microsoft services using tactics described as low-rent and intrusive.
Opening excerpt (first ~120 words) tap to expand
Software 1 Microsoft's bad obsession is showing up in shabby services and slipshod software. Here's proof 1 If you can't bother to keep GitHub running, why should we bother with you? Rupert Goodwins Tue 5 May 2026 // 08:30 UTC Opinion It's been another shabby week for Microsoft, and a shabbier one for its users. We learnt that Windows 11's epic habit of trying to corral customers into paid-for Microsoft services just got worse with a low-rent trick. Remote Desktop got a bit more secure, which is good, but in a way that suggests not too much user testing took place. As for GitHub… GitHub got two helpings of Chef Redmondo's Special Sauce.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at The Register.
Discussion
0 commentsMore from The Register
