>Written by human All opinions are my own and not those of a large language model. Everything I write is one hundred percent human. Because I care!
GitHub is sinking
101–110 of 176 posts
Re: GitHub is sinking
#102Re: GitHub is sinking
#103Everyone wants to pin this on the Microsoft acquisition or incompetence but it seems pretty clear to me from the material GitHub has posted that AI has 10xed the amount of code being committed to GH, which has downstream effects everywhere - CI, Actions, code ingestion, everywhere. The author pins it on weird things like MS Copilot, which kind of feels like he’s listing off things he doesn’t like rather than casual f…
Re: GitHub is sinking
#104Earlier quoted context omitted.
Yeah, I had the exact same response after reading the post. I mean, I'm all for jumping on the Microsoft hate train, but not if it misses the elephant in the room. Let's say the _perfect_ GitHub replacement spawns tomorrow? What's preventing the same infrastructure challenges of millions of lines of AI-generated code destroying it? I think centralized code hosting is pretty much going to get killed by AI. Just like i…
Saas code hosting seems to be the problem here. If companies self hosted, they could deal with the scaling problems themselves.
If all companies did this, there'd be no free tier on Github. You get the free tier because the SaaS customers are subsidising the free tier.
Re: GitHub is sinking
#105Earlier quoted context omitted.
The graph is not accurate, because GitHub's historical downtime data is not accurate. For example, here is a Hacker News story about GitHub being down on July 28th 2016: https://news.ycombinator.com/item?id=12178449 Here's GitHub's historical uptime graph (on which this chart is based), saying there was no recorded downtime that day, or in fact that entire month: https://www.githubstatus.com/uptime?page=40
Looks like it's not accurate by under repporting not over reporting. So their down time was likely worse!
Re: GitHub is sinking
#106Earlier quoted context omitted.
Looks like it's not accurate by under repporting not over reporting. So their down time was likely worse!
We don't have enough data to confirm if it's over or under reporting. This sample size of 1 is enough to prove the data is not perfectly accurate, but it's not enough to prove a skew bias in the data either way.
Re: GitHub is sinking
#107Earlier quoted context omitted.
Looks like it's not accurate by under repporting not over reporting. So their down time was likely worse!
We don't have enough data to confirm if it's over or under reporting. This sample size of 1 is enough to prove the data is not perfectly accurate, but it's not enough to prove a skew bias in the data either way.
I am making an assumption that if Microsoft saw a lot of false positive outages they would fix that, but might drag their feet if there was an outage that didn't get properly recorded (assuming it's automatic to begin with, it might be that a human needs remember to update it).
Re: GitHub is sinking
#108Earlier quoted context omitted.
Yes, the terrible sin of ... Hosting code where people can find it
How did people do it before github? Did everyone write everything with peek and poke?
I've been sharing GPL projects since 1999. We didn't need peek and poke (Both of which I have also used further in history...), but we managed nevertheless.
Prior to github I shared software on sourceforge (and others). Prior to that I published stuff on Freshmeat.
Prior to that I downloaded games others shared (not open source) on Happy Puppy.
Prior to that I used usenet to find and download games, shareware, etc.
Prior to that I used ftp to (IIRC) ftp.sunsite.edu, ftp.nic.fi, and others.
Prior to that I got news of new releases using Gopher.
Finally, prior to that, I actuallyy did use peek and poke to write software :-/
If github went away, and centralised repos went away, we'd still have something...
Re: GitHub is sinking
#109Earlier quoted context omitted.
Yeah, I had the exact same response after reading the post. I mean, I'm all for jumping on the Microsoft hate train, but not if it misses the elephant in the room. Let's say the _perfect_ GitHub replacement spawns tomorrow? What's preventing the same infrastructure challenges of millions of lines of AI-generated code destroying it? I think centralized code hosting is pretty much going to get killed by AI. Just like i…
Why is centralized code hosting getting killed? I'm running an opensource project, >99% of the code is AI generated, could not do this without GitHub. Ai generated source code needs a place where AIs and people can collaborate. I'm expecting GitHub to be hugely successful, but mostly for an AI audience.
Are you paying them in proportion to the resources they expend on you?
There's this thing called "sustainability", and every company needs to have it. Github cannot continue on the current trajectory where every AI-bro wants to run an agent that generates 1000s of lines of code per hour, dozens of commits per hour... and provide that for free to a few dozens of millions of users who won't pay.
That being said, Microsoft does have an opportunity here - AI-bros are willing to pay $200/m to burn tokens so Github should offer a plan for Copilot, say $400/m, that includes a repo.
If they don't ban AI agents on free tiers, they are going to be out of business soon.
Re: GitHub is sinking
#110I would really like to see what it would be like doing all code reviews over email. The repo would just be a simple vps-style server with git-only ssh access, there’d be a particular for-review/ branch namespace for code to be reviewed, and CI would just be a bot waiting for branches to show up and would mark refs as good or not by just annotating/tagging them. It could reply in the email thread with results too.
The mailing list would have a web archive viewer, naturally. That’s how you could look at old reviews. There’s tons of existing solutions for this, and it’s just html.
Chat would be on IRC with bots to archive the channels. Easy as hell.
The whole thing (except maybe the CI runners which need beefier hardware) could be done on a very cheap server.
GitHub is waaay over engineered for what you need to run a software project. Look at the Linux kernel, they just use a simple mailing list, and it’s debatably the most successful software project of all time.
Issue/bug tracking is scarier though. Because I’d probably want to yak shave my own solution and get too involved with that and not even focus on what the company does. Maybe it could be a bug tracking software company?