Microsoft turns to AWS as GitHub faces AI capacity crunch
Posted by ilreb 1 day ago
Comments
Comment by kuschku 1 day ago
- the worst infinite scroll I've ever seen making it impossible to access the footer
- the title tag doesn't seem to work properly (just shows the URL in the tab title, on Chrome and Firefox)
- 2007-style keyword stuffing in meta keywords
- the entire page is client-side react with a completely empty body?
The agency that built it even proudly states on their website that they vibecode everything: https://gradientnoise.com/
EDIT: Turns out, the articles are mostly AI-generated as well? https://blog.ryanmerket.com/how-i-built-runtimewire-a-one-pe...
> And this is the gate that lets me sleep: a story only auto-publishes if the editor says PASS, the risk score is comfortably low, a hero image exists, and it has at least one source
Comment by plaguuuuuu 1 day ago
The interslop is real. Simulacra and simulation.
Comment by ffsm8 1 day ago
Comment by patates 1 day ago
Let's be fair, it's possible to reach the footer! You keep pressing the end key for like a minute or two and 665 requests (with embedded base64 encoded images and all) later, you have your footer.
So saying it's possible to reach the footer would be technically correct - the best kind of correct!
Comment by albert_e 1 day ago
Comment by Walf 1 day ago
Comment by ryanmerket 1 day ago
Comment by jordemort 19 hours ago
Comment by mujib77 1 day ago
Comment by kuschku 1 day ago
Mobile Chrome can't show a tab title either https://i.k8r.eu/3vVCTQ.png
And the infinite scroll causes the page to constantly jump back up, again preventing me from accessing the footer
And of course with JS disabled you get nothing at all (which affects RSS readers, kindle devices, etc)
Comment by mujib77 1 day ago
Comment by ryanmerket 1 day ago
infinite scroll fixed, nojs issues fixed, and title fixed. thanks for helping QA.
Comment by kuschku 1 day ago
Comment by ilreb 1 day ago
Comment by kuschku 1 day ago
That said, I likely wouldn't have read that thread even today. I prefer engaging more deeply with fewer stories.
Another new AI benchmark result is of little interest to me, in contrast to a story about Microsoft stalling or even partially reversing the GitHub Azure migration.
Comment by amazingman 1 day ago
Comment by palmotea 1 day ago
There are so many bad and false assumptions baked into your short comment, it's hard to begin. For instance: in what world does someone have provide justification for their critique of an AI-written website, because they didn't happen to respond to some previous post?
Comment by not_kurt_godel 1 day ago
Comment by ryanmerket 1 day ago
Comment by kuschku 1 day ago
And even if it were true, how would that justify making the situation worse? We should be doing something to make the world a better place instead.
Comment by palmotea 1 day ago
Source? Or is that just self-justifying speculation?
Comment by MallocVoidstar 1 day ago
Comment by jf 1 day ago
One of the moments that stood out to me was when Robert Youngjohns (the exec) asked Tom what it would take to have GitHub move to Azure. I was surprised that Tom had a response ready, saying that IOPS were really important and that virtual disks weren’t fast enough.
Comment by winrid 1 day ago
every fucking time
Comment by jiggawatts 1 day ago
Heathen lies!
Oh, wait… we have to use it? Oh, that’s terrible…
Comment by inopinatus 1 day ago
This led me to reconsider Amazon as a whole, and I still think of it basically as a logistics firm, with the shop and the public cloud merely a monetisation thereof.
Comment by TurdF3rguson 1 day ago
Comment by anonymousiam 1 day ago
There's also this funny outcome from the SpaceX IPO: https://x.com/ICannot_Enough/status/2065449141946253390
Comment by hvb2 1 day ago
He's flying passengers? They stopped new shepherd and that was suborbital to begin with. You can't compare the 2 at all. Getting people to orbit is much much harder than 'a hop'.
On the government contracts, yes they did get some. Some through lawyers though and they still have to show that they can actually deliver. SpaceX has to deliver on HLS as well, but the ISS has one American ride up and that's crew dragon.
Comment by csbrooks 1 day ago
So AI means 14x the checkins? That's not 14x features completed, but still... wow.
Comment by N_Lens 1 day ago
Comment by shimman 1 day ago
Comment by californical 1 day ago
Comment by kcartlidge 2 hours ago
For instance with OpenClaw and similar, they often simulate institutional and short term memory with markdown files in folders. Other tooling that runs companies using agents as staff, for example, do the same - but also with files for inputs, outcomes, handovers etc.
All of this means a lot of extra churn as these kinds of files can be changing with every interaction not just every traditional commit point.
Comment by 3eb7988a1663 1 day ago
While that is (hopefully) the upper end of the distribution, several companies have loudly encouraged engineers to light tokens on fire to the AI gods, so it only takes a handful of the devout to push up the average in gas town like ventures.
Comment by BobbyTables2 1 day ago
Spread over a year, roughly estimating a generous 4 kbytes of data per commit, comes out to a throughput of a little under 2 MB/s.
Of course, it isn’t spread out uniformly and there is also a lot of hashing and other things going on.
Maybe pulls and clones drive more I/O ?
Comment by 3eb7988a1663 1 day ago
That's also just assuming the good-faith usage. There are probably plenty of adversarial and poorly behaved scrapers that are putting additional load on the system.
Comment by jamesfinlayson 1 day ago
Comment by BobbyTables2 12 hours ago
Even if they had 10 billion users with 10 billion repositories it shouldn’t be a big deal on a home PC.
Comment by Aperocky 1 day ago
Comment by nomel 1 day ago
Comment by larusso 1 day ago
We had it internally with our teams that open a PR to then push like 10-20 more commits but never actually interested in the client builds etc. turned out they opened the PR as a checkmark/ way to share the current state. We set cooldowns and auto cancel for the ci. And then there is the developer who uses the CI compute to run tests instead of running them locally for various reasons. We had to remind that compute isn’t for free.
Comment by nomel 1 day ago
Comment by ashishb 1 day ago
My belief is it is likely 1% or more. And likely coming in as an avalanche.
Comment by alibarber 1 day ago
https://github.com/aiortc/aiortc
It was fun and I found the code nice and helpful.
I clicked on the PRs to see if there was anything interesting to look at. I started reading one when I just realised I was just reading someone’s Claude talking to GitHub Copilot. That was when I decided that the Dead Internet Theory had already happened.
Comment by not_kurt_godel 1 day ago
Comment by rickette 1 day ago
Comment by theojulienne 1 day ago
If this story is true, it's good that they finally realised that GitHub's performance and availability mattered more than using Microsoft's products. It would mean someone finally came to their senses rather than forcing a wholesale push to Azure - but I bet they still want to have it both ways even if they concede some AWS now.
Comment by jeffrallen 1 day ago
Comment by collabs 1 day ago
Comment by JumpCrisscross 1 day ago
(Probably just tea leaves. If you wanted to be extra spicy, you’d note that Jassy just threw Fable under the bus.)
Comment by shrubble 1 day ago
Comment by VirusNewbie 23 hours ago
Anthropic has been very strategic about playing all the big cloud providers off each other. They're also in desperate need of inference, and I don't think AWS has the capacity to scale up as fast as they want. AWS may also be trying to 'force' them to use Graviton, and I don't think Anthropic is as big of a fan.
Comment by CSMastermind 1 day ago
Comment by amazingman 1 day ago
Comment by daft_pink 1 day ago
Comment by locusofself 1 day ago
Comment by N_Lens 1 day ago
Comment by aykutseker 1 day ago
Agents are starting to use it while they think.
Comment by pjmlp 1 day ago
Comment by UnlockedSecrets 1 day ago
Comment by kqgnkqgn 1 day ago
Comment by enigmo 1 day ago
the Solaris bits (storage and routing tables) took far longer - and again iirc the frontend had been rewritten in C# before all the Sun hardware had been decommissioned.
Comment by kqgnkqgn 11 hours ago
Comment by enigmo 2 hours ago
fun times for sure.
Comment by jeffrallen 1 day ago
Comment by pmontra 1 day ago
Comment by fortran77 1 day ago
Comment by fuckinpuppers 9 hours ago
Comment by sreekanth850 1 day ago
Comment by citizenpaul 1 day ago