it's a bit of a stretch to call removing a free tier a scam. as you can see a lot of people in this thread are saying Github should start charging.

Nobody at Microsoft could've predicted AI was going to be so popular!

It is just an excuse. If they can't support paid member or don't have infra they should start charging these slop projects who are committing relentlessly.

> Github is struggling because AI-boosted coding increased the number of commits 14x in the past year, and the pace is still accelerating.

Sure, but how is OpenAI, and Claude handling the increased usage? They are handling it a lot better than Github. Just because you have fast growth does not mean you can not handle it.

Instead you have to realize that you are entering into a high growth phase and design around that.

It has been clear that we are in a high growth phase for around a year now and Github still hasn't adapted to that properly.

At some point you have to admit that Github ready for the moment.

The obvious answer is to end free unlimited private repos. Source is no longer a specific thing. GitHub is just a free S3 or Azure provider.

Github is owned by Microsoft, its not like its some boostrapped startup who has a closet of servers that are melting.

> Github is struggling because AI-boosted coding increased the number of commits 14x in the past year,

OK so then use the additional revenue to add more resources and employees? What the f*k are they doing over there?

If that's the superficial cause, then the root cause is a lack of limits. Any production system in the world will go down from too much load if you don't limit the load. You have to do performance testing to determine what the system's peak utilization is, and put limits in place to prevent exceeding that limit.

There are multiple kinds of limits you need. First you need the raw i/o limits on things like networking, load balancer requests per second, etc so you don't slow to a crawl on high load; you can throttle max i/o so demanding users don't steal performance for others, or even throttle network traffic to the client IP and internal services. Then you need additional limits at app layer, like number of requests you can process that make DB calls (as most DBs have a connection and request limit), or limit API requests to X/minute. Then you need more business logic limits, like max number of concurrent logged-in users, max number of repos a user can have, max number of requests for free users, priority for paid requests, etc.

When you hit a limit, you have a couple choices. You can shed load (dropping calls immediately, which results in 503 errors for users, or even network disconnects), but it makes a very poor user experience, and can cause larger issues/conflicts in a distributed system. You can instead keep a max number of active sessions, and adjust that number over time, to ensure that (on average) your users have a stable experience; this requires implementing a "waiting room" for new sessions when old ones expire or log out; still not great for users, but it prevents everyone from getting random errors, which means the majority of users have a good experience.

There are way more kinds of limits to implement. Each business has to analyze its entire system to identify performance bottlenecks and implement limits to ensure the majority of users continue to have good service. Without those limits, you get a shit experience for everyone, your brand is tarnished, and customers run for the hills.

Finally, the performance testing helps you plan how much infrastructure you need to serve a given number of users. If you plan properly, you know X infra allows for Y number of users. Once you exceed Y users, you need to start throttling or stopping new user signup, until you can increase capacity. Continuing to allow signups and additional usage, without the capacity to support it, results in what we see today, which is the whole site being down for everyone.

I think that data is a bit dated and misleading, but I would love to see if AI slop is a contributing factor here once the dust settles and how Github will address it. Looking at the return to mean in https://areyougoingexponential.rhys.dev/kdaigle makes me think the COO spike could be a Karpathy wiki or an agent too.

Fundamentally, there's incoming requests, an application server, and a database. The devil is in the nature of those requests, and how do you process those requests and stick them in the database. And then serve them back out again. Different application, different database, but fundamentally, it's the same problem. Google managed to do this very well. Microsoft has not.

I am pretty sure OpenAI and Claude actually have a higher hardware cost per request that Microsoft. Github is actually most just a standard REST API app, although with some caching and git specific operations in the background. It is not as hardware intensive as GPU-based inference per quest with huge contexts and low latency.

Also Github's feature offering has been incredibly stable for the last 6 years. There isn't an excuse for it to be unstable like this.