No one forced them to migrate GitHub to switch to React. And the atrocious sleep bug in Actions long predates the AI gold rush.

Implying that MS would crater an org like GitHub within a few years is ascribing fundamental incompetence to a provably competent acquirer. Hanlon’s razor is precluded from use if there is contradictory logic.

GitHub’s mandated transfer to Azure was on hold for quite a while, Azure needed to be upgraded to handle them. Then the migration started, a multi-year effort, then the LLMs got integrated.

If you slap a 2.5 year window onto those phases you end up around a decade. That’s Enterprise timing, not slow motion.

And, critically, this is not some new emergent phenomenon today. Orgs are pulling the plug noticeably now because of massive service failures. The reputational damage has been growing over time.

Management changed, dumbish things happened, and consequences are rolling out. Even MS didn’t push the direct changes causing the issues (they did), they are responsible for avoiding and alleviating them (they didn’t). Change propagation takes time bound by the medium of transmission.

Instability is more due to mainstream traffic, combined (+ AI automation pushes on pointless repos).

They're part of a trillion(!!!)-dollar company and want to be an essential part of SW dev workflow. They ought to act like it.