[tyleo]

Beginning of the end of what? If I could have take a bet, “Will GitHub move to Azure?” a few years ago, I would have thrown money down.

This seems inevitable since the acquisition and not necessarily a bad thing. I see it as neutral.

[tacker2000]

The point is that they are prioritizing this over new features.

But since “new features” consists primarily of shoving the bloody copilot agent down everyones throat, it might not be such a bad thing.

[dmix]

That plus the new React diff viewer in beta. The old one seemed to be a simpler Web Component inside a Rails turbo frame.

I've tested the beta one and like most SPAs it doesn't scale well to large amounts of data (large numbers of files / line counts). You can feel the DOM slowing down even on a high end macbook. It even blanked out the page a couple times, another common issue when browsers are overloaded. So I switched back to the old one.

[dmart]

The new one also doesn’t consistently snap to a specific line in the URL fragment if the diff is too large, which makes sharing links problematic.

[torgoguys]

>The point is that they are prioritizing this over new features.

Good! Shoring up infrastructure vs. delivering the latest hotness is something that is rarely prioritized. I'll take boring and reliable every day of the week.

[tacker2000]

Fair point, but I believe they are just migrating for the sake of pleasing their MS overlords.

Does anyone know what infra they are running on now? AWS?

[dbbk]

You would be a fool to think the Copilot Coding Agent is not their most important feature at the moment. It's not particularly great, but it must become so.

[walkabout]

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.

[stackskipton]

Sure but it also might make them fix some of that.

[walkabout]

No, I mean inherently so. It's basically a whole stack of caching problems.