4 ms·
Well, it started just after the Microsoft acquisition, when AI did not exist, and coincided with news of Microsoft fully ingesting the GitHub team and forcing a
by kqp 6mo ago
Well, it started just after the Microsoft acquisition, when AI did not exist, and coincided with news of Microsoft fully ingesting the GitHub team and forcing architecture and priority changes, and has steadily continued since. So idk, it’s a mystery. Maybe it was caused by the thing that did not exist when it happened. Microsoft just posted on a PR blog that it’s the thing that did not exist, and they’re famously truthful, open, and altruistic.
- pluc 6mo agoIf you've worked with Azure you don't need to be explained what the problem is. I'll believe that workloads are different now than they were some years ago but... they literally are the cause for it so no sympathy from me there.