The worst part of all this is that GitHub's CTO and VP of Engineering sent out the usual "here's what we'll do to fix things" letter to their larger customers and, without exaggeration, it boiled down to: 1) "Here's a bunch of stuff we already did!" which... clearly isn't working, and 2) "We're continuing our Azure migration." also clearly not working.
So needless to say, if you depend on GitHub for critical business operations, you need to start thinking about what a world without GitHub looks like for your business and start working your way toward that. I know my confidence in GitHub's engineering leadership is at rock bottom.
I could sorta see a situation where the reality is "we're in the middle of a miserable transition and it'll clean up when we're done" but I don't think anyone has confidence that's all it is at this point.
Even that doesn’t really make sense to me, unless they’ve done it in a way where everything has to move at once.
Everywhere I’ve worked, if a migration is causing this much downtime then you kill the migration or slow it down. If every change has a 10% chance of bringing the site down, you only do a change every week or two until you can work out the kinks.
Reminds me of the bank for my business where a larger bank with terrible IT bought a smaller bank with great IT - guess which systems they standardized on? Online banking is still much worse than before and the web interface still says "will be migrated by end of 2023" for some parts. Many customers just left and complaints were widely reported in the media. I probably should leave, too.
Here are some relevant excerpts from an October 2025 article[1]:
> In a message to GitHub’s staff, CTO Vladimir Fedorov notes that GitHub is constrained on capacity in its Virginia data center. “It’s existential for us to keep up with the demands of AI and Copilot, which are changing how people use GitHub,” he writes.
> The plan, he writes, is for GitHub to completely move out of its own data centers in 24 months. “This means we have 18 months to execute (with a 6 month buffer),” Fedorov’s memo says. He acknowledges that since any migration of this scope will have to run in parallel on both the new and old infrastructure for at least six months, the team realistically needs to get this work done in the next 12 months.
If you consider that six month parallel window to have started from the time of the October memo (written presumably at the start of October), then that puts us currently or past the point where they would have cut off their old DC and defaulted to Azure only.
Whether plans or timelines changed, I have no idea of course but the above does make for a convenient timeline that would explain the recent instability. Of course, it could also just be symptomatic of increased AI usage generally and the same problems might have surfaced at a software level regardless of whether they were in a DC or on Azure.
Putting that nuance aside, personally I like the idea that Azure is simply a giant pile of shit operated by a corporation with no taste.
>It’s existential for us to keep up with the demands of AI and Copilot
if by chance the CTO reads this, as a user of GitHub I would find it really existential if GitHub continues functioning as a reliable hub for git workflows (hence the name), and I have the strong suspicion nobody except for the shareholders gives a lick about copilot or 'AI' if it makes the core service the site was designed for unusable
Why? What is the correlation between profit and shareholder sentiment (besides the fact that shareholders want said profits)? They don't really influence the operation of the business meaningfully.
Sure, but I think it's the wrong way around. Appeasing shareholders doesn't make you profitable, being profitable appeases shareholders. I think there is a wealth of evidence that appeasing shareholders actually impedes profits overall.
Incorrect. They need to appease/trick/threaten/etc those that are paying for their services. Shareholders just demand they do so at the greatest (often short term) rate.
i heard that they asked LinkedIn to do this too and they either refused or their systems were too complex so they refused to. Maybe that explains why LI availability seems ok
The New York Times has been thriving. They're profitable and their stock is near all-time highs. If the internet killed WaPo, why didn't it kill NYTimes?
As the sibling said, papers used to make money via ads and classifieds. NYTimes pivoted to games. This gives people a reason to go to NYT every day and gives them upsell opportunities to full subscriptions. WaPo and others don't have the alternate revenue source.
It's notable that they blame "our upstream provider" when it's quite literally the same company. I can't imagine GitHub engineers are very happy about the forced migration to Azure.
Having worked there around 2020-2021 there were many folks not happy with being forced to use azure and being forced to build GitHub actions based on azure devops. Lots of AWS usage still existed at that time but these days u bet it’s mostly gone.
True enough. The world is never as predictable as the computers we program, and the computers we program are never as predictable as we feel they should be.
Nobody is happy with Oracle anything! It has some users because it is free. It has paid users because Larry Ellison bribed the government. Nobody would choose it voluntarily.
A few years ago I talked to an developer advocate for Azure. I wanted to know why it took for ever when you wanted a new public IP. My take was that it felt like they went out on the internet to look for an IP to purchase from a 3rd. party. The answer I got was that do to the silos within Microsoft it might as well be a 3rd party supplier. The slowness is exactly because IPs are/were a managed by another Microsoft entity, who views any interaction, even within the company, as hostile.
I get your point, but it just sounds a bit funny when it's an artefact of corporate structure that it's true.
Like imagine if AWS was composed of separate companies for different services - Fargate was an Heroku acquisition say - and then they all went down and blamed their 'upstream provider' because they can't work without say VPC or EC2 availability.
I think that's all GP meant, it just reads a bit funny, not that it's wrong.
It's an incredible show but the finale "season" catapults it into my personal top 3 children's shows of all time. They did an incredible job of bringing it full circle and tying a bow on it. Tumble Leaf doesn't normally make you cry the way Bluey does, but the finale will have you bawling.
He co-founded and sold Segment. You think he was just at OpenAI to collect a check? He lays out exactly why he joined OpenAI and why he's leaving. If you think everyone does things only for cynical reasons, it might be a reflection more of your personal impulses than others.
Just because someone claims they are speaking in good faith doesn’t mean we have to take their word for it. Most people in tech dealing with big money are doing it for cynical reasons. The talk of changing the world or “doing something hard” is just marketing typically.
Calvin works incredibly hard and has very little ego. I was surprised he joined OpenAI since he's loaded from the Segment acquisition, but if anyone it makes sense he would do this. He's always looking to find the hardest problem and work on it.
That's what he did at Segment even in the later stages.
Newborns need constantly mom, not dad. Moms need husbands or their moms to help. The way it works is you agree what to do as a family (to do it or not to do it) and everybody is happy with their lives. You can be a great dad and husband and still do all of it when it makes sense and your wife supports it etc. Not having kids in the first place could be considered ego driven, not this.
No, he's right. I just went through newborn phase right now and the only person that needed is mom. Kid wanted nothing to do with me. He just wanted food and sleep.
The Café was my second home as a rural teenager into Macs and programming at a time when no other kids were. The 90s being what they were, my mom even let me fly solo to meet other Café members at the old MacHack conferences (in Dearborn, Michigan!).
I have nothing but fond memories of the 90s Mac community. It really was a special time and place. I hope my kids find their equivalent of these spaces.
Debunked isn’t the correct term here. That would imply that the data is false or it’s misinformation. Instead the article you linked states:
On the other hand, data on this issue is mixed, and some studies contradict one another.
So a better way to talk about it is that the data doesn’t yet make a cut or dry case one way or another.
Another quote from the article you linked
Haidt argues that waiting for stronger evidence could be even more dangerous. He writes: “If you listen to the alarm ringers and we turn out to be wrong, the costs are minimal and reversible. But if you listen to the skeptics and they turn out to be wrong, the costs are much larger and harder to reverse.” … as a mother, as someone who writes about the harms of tech and tech companies, I see his point.
So even if we don’t take the data to be 100% convincing, it’s by no means “debunked” and something that we should just completely ignore.
I haven't looked at Homebrew since that got started. The philosophical difference at that time was using macports and having a consistent and managed */local/ collection of tools with self contained dependencies vs. adding new tools with dependencies tied to the current Mac OS release.
I still use MacPorts for that reason and it is easy enough to create a local portfile for whatever isn't in Macports.
I find this to be the easy way to manage networked development computers.
I used MacPorts a decade ago, but at some point realized that Homebrew had more packages that were kept consistently up-to-date. Switched and never looked back.
I switched away back to macports when homebrew decided to get rid of formula options. To be honest, I always find homebrew frustrating, it feels that they've often made technical decisions that are not necessarily the best but they've been much more successful at marketing themselves than macports.
oh, I actually hadn't realized that this is what they settled on in the end. ffmpeg is the quintessential package where options make sense so good that that's still supported.
The other issue I experienced with homebrew around that time were related to having different versions of openssl installed because I had some old codebase I had to run (and for performance reasons didn't want to use docker). But that's definitely a edge case.
I’m a full-time Mac and iOS developer, have been for almost 20 years, and this is the first I’ve heard of it. Might just be my bubble, but I don’t think it’s a huge thing yet. (I’m going to check it out now!)
it's worth noting for Homebrew users that it also has a nice built-in module for managing a Homebrew installation by generating a Brewfile for you. So you can transition at your own pace, if you like
>Why is it funny? Homebrew is the de facto standard terminal packaging tool for macOS.
It's funny because a multi-trillion dollar company can't be bothered to release a native package manager or an official binary repository for their OS after decades of pleading from developers.
They released "App Store" for the average Joe. We can all agree it is not suitable for power users, but at the same time what would power users gain over existing solutions if they were to introduce something?
"Sherlocking" can be unfortunate for a developer, but it's odd to view it as an inherently bad thing. A package manager is a core OS feature, even Microsoft has WinGet now.
It has become a core OS feature. Historically, you see the set of core OS features expand tremendously. Back in the 80’s drawing lines and circles wasn’t even a core OS feature (not on many home computers, and certainly not on early PCs), bit-mapped fonts were third part add-ons for a while, vector-based fonts were an Adobe add-on (https://en.wikipedia.org/wiki/Adobe_Type_Manager), printer drivers were third party, etc.
I think that’s natural. As lower layers become commodities (try making money selling an OS that only manages memory and processes), OS sellers have to add higher layer stuff to their products to make money on them.
As to Sherlocking, big companies cannot do well there in the eyes of “the angry internet”:
- don’t release feature F: “They don’t even support F out of the box. On the competitor’s product, you get that for free”
- release a minimal implementation: “They have F, but it doesn’t do F1, F2, or F3”
- release a fairly full implementation: “Sherlocking!” and/or nitpicking about their engineering choices.
So needless to say, if you depend on GitHub for critical business operations, you need to start thinking about what a world without GitHub looks like for your business and start working your way toward that. I know my confidence in GitHub's engineering leadership is at rock bottom.
reply