News for hackers. Stuff that matters.

A comment on Incident with Github.com. Parent comment

Re:Incident with Github.com by frollogaston on Monday August 17, 2026 @04:12PM (#49336903)
It's easy from an armchair to say things like they should just get more capacity, or they should segregate free repos onto other servers. But maybe they are doing all that, and with that churn you get mistakes that cause outages. I've been there (not at GitHub or MSFT).
[ Parent | on HN ]
Re:Incident with Github.com by sqren on Monday August 17, 2026 @05:01PM (#49337573)
They do not need to make any technical changes. They could make the change overnight: $1 per repo per month (or whatever). This would stop the aggressive growth that they clearly cannot handle anyway.

The question is: are they willing to compromise growth for QoS. So far the answer is a resounding: "no". They are deliberately sacrificing the experience of existing users to gain new ones.

[ Parent | on HN ]
Re:Incident with Github.com by frollogaston on Monday August 17, 2026 @05:07PM (#49337652)
There are tons of existing free users, they'd be sacrificing those too. And yeah they don't want to sacrifice growth either, so the remaining is an engineering question.
[ Parent | on HN ]
Re:Incident with Github.com by ksbd-pls-finish on Monday August 17, 2026 @05:30PM (#49337916)
No way I pay $1/repo/month. No way I pay $1/repo/year. I still host and maintain my old code on GitHub, but any free tier pricing update and I jump ship immediately.
[ Parent | on HN ]
Re:Incident with Github.com by matkoniecz on Wednesday August 26, 2026 @07:04PM (#49457122)
I would migrate my 246 repositories before paying even a cent.
[ Parent | on HN ]