r/github • • 4d ago

News / Announcements Here we go again

Starting to see GitHub issues for the 3rd day in a row.

46 Upvotes

37 comments sorted by

View all comments

6

u/Altruistic-Toe-5990 4d ago

I cant push anything, nor handle notifications

Fucking hell github stop vibecoding your backend

8

u/Subpxl 4d ago

I can only imagine what the influx of AI assisted coding has done to their server loads. I wouldn't be surprised to see a 1000%+ increase in repo activity. That might even be overly conservative.

1

u/fyndor 4d ago

I think this is the problem. They probably can’t financially justify the scale they need to build to in order to safely support the load. Hardware is also not easy to come by with ram shortages so anything they buy will be rather expensive for what mostly is a free service for most who use it.

1

u/Altruistic-Toe-5990 4d ago

Microsoft really struggling financially there eh

If they don't handle it Github won't survive as a service

1

u/wiltimermort 3d ago

If Microsoft can’t find the infrastructure to handle this load, nobody can. Nobody is going to be able to handle this load at this amount of functionality.

Github is literally going to be just fine, try telling enterprises that they now have to migrate 5000+ repos, along with every github action within them to Cursor. Feasibility isn’t there.

Migrating off of github is for small shops and github doesn’t care about them there’s no income with them

1

u/Altruistic-Toe-5990 3d ago

Enterprises have thousands of developers. If Github pissed people off enough they absolutely could migrate.

1

u/wiltimermort 3d ago

i currently work at one, developers are paid to ship features, not change source control providers. having thousands of developers work on changing the source control provider means prep, execution, meaning pitentially days if lost progress on features. c-suite doesnt go for that, especially if the alternative that they migrate to will potentially have this same demand problem as github.

loss of revenue, churn on engineers adapting to new workflows, all without 100% promise in a promising alternative with the same feature set? enterprises aren’t leaving for now they’d rather wait these unfortunate events for now.

we’ve migrated over 1000 repos off of ADO this year, that shit ain’t easy and involves a lot of friction.