Live data from Hacker News

Microsoft turns to AWS as GitHub faces AI capacity crunch

runtimewire.com

71–80 of 83 posts

Re: Microsoft turns to AWS as GitHub faces AI capacity crunch

#71
post #56
post #49

Earlier quoted context omitted.

works fine on the phone

I can't confirm that. 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)

rss is fine /rss

infinite scroll fixed, nojs issues fixed, and title fixed. thanks for helping QA.

Re: Microsoft turns to AWS as GitHub faces AI capacity crunch

#72
post #56

Earlier quoted context omitted.

I can't confirm that. 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)

rss is fine /rss infinite scroll fixed, nojs issues fixed, and title fixed. thanks for helping QA.

Typically, you'd want to be able to fetch the full article with your RSS reader, which obviously doesn't work with client side rendering.

Re: Microsoft turns to AWS as GitHub faces AI capacity crunch

#73

Earlier quoted context omitted.

> https://news.ycombinator.com/item?id=48440448 this had >300 upvotes with a link from runtimewire.com and you didn't even criticize it then. why now? 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?

almost every news website is written primarily by AI these days with a human editor to review...

That's not even close to the truth, there's a lot more manual work that still goes into news than you'd think.

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.

Re: Microsoft turns to AWS as GitHub faces AI capacity crunch

#74

If there’s one thing that surprised me at AWS during my time there - over a decade ago now - that I was not clearly expecting in advance, it was the scale and competence of the units fulfilling the colossal and unceasing growth in capacity demand. 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.

I wonder how that translates to Blue Origin and how they managed to be so completely outclassed by SpaceX.

[deleted]

Re: Microsoft turns to AWS as GitHub faces AI capacity crunch

#75

Interesting to see Anthropic go with xAI and Microsoft go with Amazon. (Probably just tea leaves. If you wanted to be extra spicy, you’d note that Jassy just threw Fable under the bus.)

>Interesting to see Anthropic go with xAI and Microsoft go with Amazon.

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.

Re: Microsoft turns to AWS as GitHub faces AI capacity crunch

#76
post #36

What kind of vibecoded website is this? - 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…

yeah, pointless AI-generated header image --> close tab

Re: Microsoft turns to AWS as GitHub faces AI capacity crunch

#77

Earlier quoted context omitted.

I suspect there is a cacophony of work that happens when a commit hits the server. That request needs to get replicated, git repositories need to be repacked, pull requests need to calculate diffs, CI jobs need to execute, on and on. 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.

Recalculate percentage of each language in the repo, recalculate top contributors, recalculate the stats for the committer's profile etc etc.

Scalable algorithms and data structures have existed for decades.

Even if they had 10 billion users with 10 billion repositories it shouldn’t be a big deal on a home PC.

Re: Microsoft turns to AWS as GitHub faces AI capacity crunch

#78
post #61

Earlier quoted context omitted.

I'm not sure if it was entirely true, but there are stories that after Microsoft bought Hotmail in the mid-90's, they quickly attempted to move them from FreeBSD (?) to Windows NT. But it failed miserably, and they went back to the original stack for another ~decade.

the FreeBSD migration didn’t take that long - iirc this was the frontend migration to an IIS ISAPI. 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.

Ah sounds like you actually might have been there. I'm sure you must have some interesting stories from that time

Re: Microsoft turns to AWS as GitHub faces AI capacity crunch

#80
post #2

> commits were on pace to hit 14 billion in 2026, up from 1 billion in 2025 So AI means 14x the checkins? That's not 14x features completed, but still... wow.

With agentic stuff there's also a large amount of commits which are not code.

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.

Post reply on HN