This is good news right? People complain about them having bloated it with too many features. If this keeps them from making it even more of an ridiculous AI editor rather than something that complements an editor, that would be great.
GitHub will prioritize migrating to Azure over feature development
21–30 of 67 posts
Re: GitHub will prioritize migrating to Azure over feature development
#22> It’s existential for us to keep up with the demands of AI and Copilot, which are changing how people use GitHub,” he writes.
yes, the addition of un-disableable "AI" features made me spend a large amount of time and effort moving every single one of my projects off GitHub
Re: GitHub will prioritize migrating to Azure over feature development
#23> 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…
[dead]
Re: GitHub will prioritize migrating to Azure over feature development
#24> It’s existential for us to keep up with the demands of AI and Copilot, which are changing how people use GitHub,” he writes. yes, the addition of un-disableable "AI" features made me spend a large amount of time and effort moving every single one of my projects off GitHub
[flagged]
Re: GitHub will prioritize migrating to Azure over feature development
#25Earlier 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.
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.
Re: GitHub will prioritize migrating to Azure over feature development
#26Does this mean GitHub will finally support IPv6?
Re: GitHub will prioritize migrating to Azure over feature development
#27> 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…
This discrepancy is precisely the reason (or at least one reason) why AI 2027 hypothesizes that all the interesting developments will be happening inside whichever AI lab is in the lead. The kind of AI agent that AI 2027 hypothesizes in that timeframe could do the migration in much less than 24 months, but only if the organization completely changes how it works internally so that everything is driven by the goal of exploiting the AI's capabilities to the maximal extent. Microsoft/GitHub probably can't do that that quickly.
Re: GitHub will prioritize migrating to Azure over feature development
#28I'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.
When I was on infrastructure at Adobe, similar migrations took around 8-9 months (e.g. expanding into Azure, modernizing our datacenters, switching to Kubernetes).
The quote says the effort is to move "completely".
I think there will probably be a long tail which will prevent that from happening so quickly.
(It also probably doesn't really matter... if their main goal is to scale using azure they really only need the stuff that will be scaling up to be there. They probably also want to be seen as eating their own dog food, which can reasonably be achieved without all of the long tail.)
Re: GitHub will prioritize migrating to Azure over feature development
#29This is, as they say, "The beginning of the end."
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.
Re: GitHub will prioritize migrating to Azure over feature development
#30I'm kind of neutral on this... It was more than expected since the MS acquisition and my biggest surprise is that both it didn't come sooner and that they're making the relatively sane choice to clearly prioritize getting the environment shifted instead of juggling multiple "priority" projects and features.