Microsoft turns to AWS as GitHub faces AI capacity crunch
31–40 of 83 posts
Re: Microsoft turns to AWS as GitHub faces AI capacity crunch
#32(Probably just tea leaves. If you wanted to be extra spicy, you’d note that Jassy just threw Fable under the bus.)
Re: Microsoft turns to AWS as GitHub faces AI capacity crunch
#33Re: Microsoft turns to AWS as GitHub faces AI capacity crunch
#34Interesting 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.)
Re: Microsoft turns to AWS as GitHub faces AI capacity crunch
#35Interesting 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.)
Re: Microsoft turns to AWS as GitHub faces AI capacity crunch
#36- 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
Re: Microsoft turns to AWS as GitHub faces AI capacity crunch
#37What 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…
Re: Microsoft turns to AWS as GitHub faces AI capacity crunch
#38Easy to criticize this, but I rather see GitHub survive than fail under its own success. So thanks for acting on this MS!
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.
Re: Microsoft turns to AWS as GitHub faces AI capacity crunch
#39Re: Microsoft turns to AWS as GitHub faces AI capacity crunch
#40https://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.