The infrastructure behind serving git repos the way they do is pretty fiddly—I'd not be a bit surprised if this move reduces stability and/or performance.
That started with MS and accelerated with Copilot. Word is that GH leadership doesn't care about anything other than Copilot/AI. All other features are receiving far less focus and fewer resources. I've heard this repeatedly from current and former employees.
IMHO: the acceleration curve into point-of-no-return was when Microsoft decided to go hard on AI, and saw GitHub's Copilot as one of the key inflection points they were going to use to do so - even going so far to adopt the Copilot brand across the entire company.
Before that, it still felt like there _some_ degree of autonomy and ability to think about the developer experience on the platform as a whole. Once ChatGPT took off and MSFT decided that they were going to go hard on AI, though, Copilot (and therefore GitHub) became too important to Microsoft to leave alone.
I kinda suspect the slide was inevitable anyway, given how acquisitions tend to go. But IMO, Copilot was the tsunami that washed the octocat out to sea.
tyleo|4 months ago
This seems inevitable since the acquisition and not necessarily a bad thing. I see it as neutral.
tacker2000|4 months ago
But since “new features” consists primarily of shoving the bloody copilot agent down everyones throat, it might not be such a bad thing.
walkabout|4 months ago
driverdan|4 months ago
aaronbrethorst|4 months ago
rufo|4 months ago
Before that, it still felt like there _some_ degree of autonomy and ability to think about the developer experience on the platform as a whole. Once ChatGPT took off and MSFT decided that they were going to go hard on AI, though, Copilot (and therefore GitHub) became too important to Microsoft to leave alone.
I kinda suspect the slide was inevitable anyway, given how acquisitions tend to go. But IMO, Copilot was the tsunami that washed the octocat out to sea.
bediger4000|4 months ago