GitHub will prioritize migrating to Azure over feature development
1–10 of 67 posts
Re: GitHub will prioritize migrating to Azure over feature development
#2This is, as they say, "The beginning of the end."
Re: GitHub will prioritize migrating to Azure over feature development
#3This is, as they say, "The beginning of the end."
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.
Re: GitHub will prioritize migrating to Azure over feature development
#4While GitHub had previously started work on migrating parts of its service to Azure, our understanding is that these migrations have been halting and sometimes failed
And there's no reason to suspect this next batch of migrations will be any different. Telling your engineers, 'good luck, you get to spend the next 18 months treading water,' is a terrible way to get them to give their best or even stick around.
Re: GitHub will prioritize migrating to Azure over feature development
#5This is, as they say, "The beginning of the end."
nah, I'd say we're well past that. The beginning might have been Microsoft's acquisition of GitHub. Or the elimination of GitHub's independence.
Re: GitHub will prioritize migrating to Azure over feature development
#6> The plan, he writes, is for GitHub to completely move out of its own data centers in 24 months.
I find it interesting to compare timelines like this (which is very reasonable and expected for an organization of Github's size) with, for example, how AI 2027 describes the world will look like in October 2027.
In the next 24 months, if all these timeslines are to be believed, AI will have cured cancer, agent-5 will be plotting to kill all humans, leveraging all the data in a Global Central Memory Bank to subvert the internal corporate politics of all companies, governments, and militaries toward this goal (These are all real predictions AI 2027 makes); and Github will still be migrating workloads to Azure.
Maybe they should get agent-4 to help them.
Re: GitHub will prioritize migrating to Azure over feature development
#7This is, as they say, "The beginning of the end."
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.
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.
Re: GitHub will prioritize migrating to Azure over feature development
#8I've never done a migration at a scale like this, but I have seen infra at similar scale, and I can't imagine how difficult this will be in a 12 month period. How big are github's ops/dev teams? That seems like a really unrealistic target to me. I expect outages.
Re: GitHub will prioritize migrating to Azure over feature development
#9Earlier quoted context omitted.
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.
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.
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.
Re: GitHub will prioritize migrating to Azure over feature development
#10This is, as they say, "The beginning of the end."
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.
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.