I know this is ridiculously dramatic, but its the truth: I actually cried writing this blog post (tears hit my keyboard, I'm embarrassed to say).
Nobody should cry over a SaaS, of all things. But GitHub has meant so much more to me than that (all laid out in the post). I have an unhealthy relationship with it. Its given me so much and I'm so thankful for it. But, it's not what it used to be. I don't know.
We've been discussing it off and on for months, really started seriously discussing it a couple weeks ago, and made the final decision a few days ago. Putting metaphorical pen to paper and hitting "publish" makes it so very real.
I'm sure folks will make fun of me for this. It is a stupid thing. But I truly love GitHub, and I hope they find their way.
It's okay to have emotions. I have similar emotions. I'm GitHub User 22723 which is effectively the same as you (considering there's ~180m GH accounts nowadays)
My version of your post reads differently:
"GitHub only gets better if people who give a shit stick around to make it better"
Walking away would be easy. I felt that way when I left Heroku ~six years ago. I left that job and never opened the Heroku dashboard again, after nearly a decade of happy use. I felt that it was irredeemable, and though it took a while, Salesforce did eventually succeed in running it fully into the ground.
I don't feel the same about GitHub. It is precisely because it's precious that I can't walk away. I'm not the only one here who feels that way.
In the past few years, GitHub has absorbed both a fundamental paradigm shift (agentic coding) AND several different hockey sticks of growth. It's messy. I'm not always proud of the results or the product choices we are forced into. But none of it feels like the Heroku/Salesforce debacle. Occam's razor applies here: it's not "more AI coding" and it's not "big bad Microsoft." It's scale, and a fundamental shift of the ground under all of our feet.
I hope we do the things that will make you want to come back. I hope we spark that joy in you again! It's not stupid to have big feelings about something that is so central to our lives as developers. Fuck that noise.
> "GitHub only gets better if people who give a shit stick around to make it better"
It is a megacorp that is mainly in this situation because of its relentless pursuit of exponential growth for the benefit of a very select few to the detriment of everyone else (including GitHub employees such as yourself). The hockey sticks are there, but how they've reacted to them - which is what has lead to this situation - is entirely because of the above. If not for that, it could've reacted to them differently.
It does not deserve to get better.
It would be very good for society if GitHub's market share massively declined, if everyone moved away. It wouldn't be good for you personally, but it would be good for everyone else. There is nothing positive about a single company having access to everyone's code.
Just look at all the tricks you've been playing, automatically opting everyone in to having their code used for LLM training. [0]
GitHub shouldn't get better. It should decline in popularity.
You know full well that it is undeniable that your competitors gaining market share would be good for everyone as a whole, but comp juicy and emotional attachment to people there and the pre-acquisition times where it used to be a great company (those times are not coming back) and your past with them etc.
I used to think people who said Github had become very unreliable were exagerating, but I can't miss it now. If you want to keep people, you have to actually go down less.
It's interesting that internally you had a very different experience with Salesforce buying Heroku and Microsoft buying Github. From the outside it appears to be analagous (except github is degrading quicker than Heroku did?)
Just an observation: The different approaches mentioned in the replies to this post seem to all neatly fall into one of the three types of individual response (exit, voice, loyalty) there are to any sort of decline in/of firms and organizations of any kind within Albert O. Hirschman's well-known economic framework, originally laid out in Exit, Voice, and Loyalty: Responses to Decline in Firms, Organizations, and States (1970).
Personally, I find "loyalty" perhaps the most fascinating one of those, being "irrational" for the individual almost by definition but sometimes, for example, proving out to be the only "glue" holding an organization together through a period of incurable-looking decline followed by an eventual recovery (in the lucky cases).
> "GitHub only gets better if people who give a shit stick around to make it better"
At a basic level I appreciate this sentiment. However, the common dysfunction I see in large corporation is its not the lack of people who give a shit. Its lacking a sufficient number of people in positions of power that give a shit -- such that they can actually make change happen.
All too often competing pressures (features, profit, delivery speed, politics) take precedence; not leaving time for things that would really move the needle. In essence, too many leaders are happy to ship garbage; they don't care (or don't know).
If Github were to put out a statement saying "service quality is our priority", it is fairly meaningless. If they added "here's how we'll get there", maybe it helps some. Moreso -- "from now on executive compensation is tied to these SLOs", then maybe something would actually happen.
> "GitHub only gets better if people who give a shit stick around to make it better"
What's the mechanism of action here? What changes if I stay? What changes if I give more or less of a shit? Is there javascript telemetry feeding my shit into a dashboard with a calibrated shitometer for executives to consult when they set quarterly objectives? My account is six weeks younger than mitchellh's and I've been watching GitHub fall apart for the last year, what will happen because I stick around to watch for another year? Besides that I will get covered in shit.
You're an employee. What changes if you stick around? Back in October 2025, the GitHub CTO Federov prioritized moving to Azure above feature work (https://thenewstack.io/github-will-prioritize-migrating-to-a...). Yesterday he recommitted to it (https://github.blog/news-insights/company-news/an-update-on-...), writing "We started executing our plan to increase GitHub’s capacity by 10X in October 2025 with a goal of substantially improving reliability and failover." GitHub has had six bad months of increasing bugs and sharply decreased uptime, and the CTO just recommitted to staying the course. You've explicitly been directed to move to Azure, not to give a shit or to make things better.
So I'll defer to your direct expertise. From the outside, Heroku stalled and died because Salesforce prioritized everything else in its business above Heroku. Are GitHub's priorities so different? Does you giving a shit make Azure and Copilot the best top priorities for GitHub? Will Azure and Copilot be why I stop seeing SPA jank? Will Azure and Copilot be why I can see my list of open PRs? Will Azure and Copilot be why I see something more than the 500 unicorn? Will Azure and Copilot stop the spam PRs that want to undermine the quality of my code? Will Azure and Copilot lead to anything other than the same corporate dismissal and dysfunction that led to Heroku? Will you giving a shit matter?
> In the past few years, GitHub has absorbed both a fundamental paradigm shift (agentic coding) AND several different hockey sticks of growth. It's messy. I'm not always proud of the results or the product choices we are forced into.
Excellent example of why centralization is a bad thing. A Git “hub” is not a thing that should have ever existed for a self-described “distributed” version control system.
> t's not "more AI coding" and it's not "big bad Microsoft." It's scale
Besides "That's what makes us money and pays my bills", there is no real reason to keep building github as this centralized, all-encompassing system that needs to work at global scale.
Engineering is about understanding that everything is about trade-offs, and eerything keeps pointing out to the fact that wrong choices are being made there. You can throw as many people as you want or all the MS money at it, but as long as Github "engineers" that keeps overindexing on Efficiency at the cost of Resiliency, it will feel like this pile of unusable crap
I completely understand a "people who give a shit stick around" mentality if you work there, but you can't expect users who run a business on it to stick around if it's broken.
Github is Microsoft, who even cares? How can ppl be so caught up in a brand name? Microsoft doesn't care about you, why do you care about Microsoft? Things always change, just move on when the time is right.
I found out today that I am user 6082. I have been using github since the rubyconf (railsconf? I can't remember) where it was announced. I loved octocat. I was a git fanatic. It has been extremely disappointing.
I am using fossil now. I kind of love it, just a sqlite file with a very trim binary to interact with it. I get all of my things that I want (wiki, forum, issues, docs, etc) all in one file.
But that's just for fun. At work we are still tied to Microsoft Github. Just typing that out feels dirty.
github hasn't absorbed agentic coding, though. agentic coding has absorbed it, and as a result it's quality is suffering.
the thing about github that is so maddening is linus gave us the secret with git itself. then we reinvented centralized source control using git and called it github, and here we are.
As someone with the ID 1653, I've totally given up on the thing. I've even created my own rust based forge, ironically, hosted on github at the moment.
> My version of your post reads differently:
> "GitHub only gets better if people who give a shit stick around to make it better"
> Walking away would be easy.
Yeah, be careful not to gaslight yourself into trying to "tough it out" with bad vendor relationships. Sometimes you do need to know when things aren't good/healthy and it is time to walk away, as sticking around just ends up being needlessly flagellent.
Especially with corporate owned software or SaaS ecosystems!
Sounds like you made the right choice with Heroku back in the day. I feel like this is Github's Heroku moment.
Considering the size and scale of Github, do you feel like it's become closer to an infrastructural public good rather than a privately owned product?
The amount of impact I've seen to businesses around the US at least might as well be akin to a Covid shutdown, and that certainly has me thinking about what the overall impacts are on the US economy overall.
I appreciate that you're staying inside with that mentality.
Like Mitchell, GitHub was once a dream job for me, and it just never lined up pre-acquisition. I shared many of Mitchell's habits too, about GitHub being my reading material. Until some time after passing 2000 starred repos, I had literally read every line of code in each of them. GitHub still feels like home to me, as a user.
Good luck, and we're all counting on you.
(359439, which is quite high for this thread, it seems!)
As Albert Hirschman observed in reflecting on his seminal "Exit, Loyalty and Voice": "an organization needs minimal, or floor, levels of exit and voice in order to receive the necessary feedback about its performance".
Don't feel too bad, you are both essential to the process that ends in Github improving (or imploding).
The heroku mention here struck a chord for me. I don’t feel as attached to GitHub for some reason but Heroku was the first web host I used where I felt like “this is how cool a web-based tech-oriented product can be”.
So crazy to see how money can ruin such a good thing.
Github isn't a public good or a person; it's a product for a for-profit company, whose aim is to squeeze profit out of you. They care nothing for you and will dump you the moment it's profitable.
I would invest your energy in something worthwhile like an open source project, a non-profit, a social or political cause, a family memeber, etc.
> Occam's razor applies here
I think the simpler explanation is clearly that it's a for-profit company and these problems aren't worth fixing, and not a speculative engineering excuse. If Microsoft wanted to invest more, including in uptime, they could make it happen. They have over a trillion dollars.
What you built was a community, not a website owned by Microsoft — it could port just fine to GitLab.
“I won’t leave, I’ll fight to make this place better!” is a laudable trope ofc, but in this case you’re not making any place better, you’re just defending shareholder value. IMHO :)
"GitHub only gets better if people who give a shit stick around to make it better"
This only works in democratic settings. In capitalist corporations, typical liberalist parliamentarism and so on it does not work, only coercion does, which might be peaceful, like a strike or boycott, or it might not be.
fuck microsoft. it absolutely is the big badness of that monster. microsoft's sick monopoly has dragged humanity back by years from where we should be. every hour wasted, every email lost, every skilled career sacrificed to their garbage is the future lost.
Hi, tangential but your post mentions only two pronouns when the recent trend is to mention 3 out of respect for gender fluid people who often use slight deviations in the third pronoun as an indication of their fluidity. Hope you do better
I can feel the frustation, nothing dramatic about expressing it
This quote from the post resonated with me:
> I want to get work done and it doesn't want me to get work done. I want to ship software and it doesn't want me to ship software.
The sentiment is shared, and github is not the only service making me feel like that, it feels like everything on the web is more flimsy and low quality nowadays. Constant outages, bugs, UI papercuts, incomplete features, what in the world is going on?
> it feels like everything on the web is more flimsy and low quality nowadays.
Not just the web either. It feels like the whole world is in a race to throw shit together and cash out as quickly as possible: influencers, hustle culture, enshittification, etc.
My pet theory is that all of the global chaos around the climate, politics, pandemic, etc. is leading people to no longer believe in the future. Once you lose that, all that's left to care about is the right now. No one takes the time to scrimshaw the deckrails on a ship they believe is sinking.
> I can feel the frustation, nothing dramatic about expressing it
I think the "ridiculously dramatic" part is the whole love letter to GitHub, not the frustration.
And I think it is fair to say that it is ridiculously dramatic. Which is okay, of course, I'm not criticising here. Just like it would feel ridiculously dramatic (at least to me) if someone explained that they cried today when they stopped their subscription to Netflix in order to move to another service, because they love Netflix so much.
>The sentiment is shared, and github is not the only service making me feel like that, it feels like everything on the web is more flimsy and low quality nowadays. Constant outages, bugs, UI papercuts, incomplete features, what in the world is going on?
Have you ever tried to run anything from the 80/90s era? Segfault everywhere, "fatal error was successful", kernel panic, BSOD, screen freeze for any reason and its opposite.
Nothing serves better good all time than bad memory as they say.
Not that the gigabit of useless crap to show essentially a few ko of text is fine, but the abuses and horrors that humans commit just shifted a bit where they land, it's not like there was a time were we had a land free of human dirty stuffs.
To be honest, the blog post is quite a lot of self-indulgent waffle. But I forgive you for that, "each to their own", as they say.
What I won't forgive you for is writing such a long blog post and then completely missing the bottom-line.
Do not write "I'll share more details about where the Ghostty project will be moving to in the coming months".
If you're going to make me read such a long blog post, then at least have an answer ready-to-go for the critical question that everybody is going to ask !
Spool of Wire Guy or Wiregate refers to a viral video of a man (named Dan) telling his wife (Cindy) that a spool of wire he's had for 40 years is almost at its end
The spool of wire became a prominent metaphor on the app, representing something that might seem meaningless to others, but holds sentimental and nostalgic value to its owner.
I do recall this meme and I empathize with him and also Mitchell above. It's annoying for people to not understand your feelings or make fun of them especially if they're reflections on years past.
There isn't inherently wrong with loving a tool or been sad when it it becomes something you can't love anymore, we are tool using monkeys after all - it is perhaps our defining characteristic.
I'd be absolute crushed if Linux (for example) morphed into something I could not/no longer wanted to use, part of the reason I use open source wherever I can is because that is less likely to happen, Inkscape is still inkscape nearly 20 years after I started using it, so is Gimp, so is KDE, they've all changed but the essence of them is still the same (so has Linux).
KDE's hard-switch to Wayland broke so many things in my workflows, from what used to be a perfect system.
For keyboard expansions espansso/ydotools crash bi-hourly and I couldn't pinpoint the source, clipboard sharing between applications doesn't work anymore, global shortcuts have been limited... The essence is the same, but it is so broken that it has a real productivity impact that will require a lot of effort to correct, and would depend on upstream fixes...
Nothing stupid about caring deeply about tools that shaped your career. GitHub wasn't just a SaaS for a lot of us it was where we learned to build. The fact that you're emotional about it says more about how much you gave to that platform than anything else.
Ghostty will be fine wherever it lives because people follow the project and not where it's hosted. Best of luck!
So true! This quote from the blog post really hit me:
> Since then, I've opened GitHub every single day. Every day, multiple times per day, for over 18 years. Over half my life. A handful of exceptions in there (I'd love to see the data), but I can't imagine more than a week per year
How could you not feel this way about a tool you willingly use this much? Perhaps if your employer is forcing you to use it, its different. But maintaining OSS? that's a labor of love. How could you not get emotional?
That is indeed a dangerous slip. I hope yours wasn't an Apple machine. Warranty might be an issue, because even if just one key got soiled, they will propose you should replace "practically" the entire machine (or rather make you; because well, replacing just that exact part that was damaged would be less expensive and hence less efficient and environmentally unfriendly).
On the other hand, not at all ridiculous; dramatic yes. I almost felt sad when Orkut shut down. Almost. And around the time XMPP/Jabber stopped being like email when Google/Fb pulled the plug. Can't remember whether it was at the same time. I became numb to such fast and slow metamorphoses a long time ago and I feel sad about this numbness. It's a forced cynicism I'd say. These are such inane corporate events/changes and yet these are so deeply embedded in our lives. Without check and any power over them. So perpetual cynicism works.
PS. I really found Ghostty to be cool (and fast!). Sadly, I reverted to stock Terminal, not because Terminal is as good, but because I no longer have/had much terminal usage (until I get back to work/coding again, and I hear things are happening in the terminal a lot more again with our world's new coding toys, LLMs, and whatnot). I also heard you on a podcast recently, and it was very interesting, and since then, I want to try Ghostty again, without even a real need for it yet.
I feel you mate. When people were scrolling Facebook, I was scrolling github, being so excited to see so many people building things together. Commits popping up in my stream were making me feel we were improving the world, bit by bit. It was an happy stream, compared to the depressing stream of Facebook.
And then Microsoft bought github. And I knew it would only be a matter of time before it would fell down. It also made little sense to build all our beloved open source projects in the living room of the entity who was so harmful to our community for years.
So I left github and joined several gitlabs. But I never found back this central steam of "look at open source being made in real time". We need a decentralized gitlab with ActivityPub.
We weren’t even in the same circles and this was my first good conference, but my own little company that I worked at was full of motivated hackers that were trying to wrap our heads around what you already understood.
You took my comments about on-boarding and documentation very humbly and you knew what I was really saying was: keep it up.
You sure did keep it up.
Those same team mates are here with me using TF at a different company years later, and we’re still pushing left.
Those colleagues just said “it’s art and science”
… and when the art gets ripped away from you, what you described is a natural reaction.
> I truly love GitHub, and I hope they find their way.
I jumped ship as soon as they added MFA. I vibe-coded my own raw Git repository reader to help consolidate my other repos (BitBucket, GitLab), which inevitably started to impose more restrictions (disk space, MFA), as well. It's no GitHub, but works, doesn't cache, and is pure PHP.
I hope this doesn’t come across as making fun, but it had never occurred to me that GitHub could be anything more than a tool for hosting my source code. So if you had written this same piece about all the good times you’d had in Windows Explorer, I’d be no less confused.
Can I ask what was there that made you visit the site for anything other than reviewing pull requests and issues?
It's probably not GitHub as such, but the associated memories and experiences. You never miss a place, you miss the feeling of happines you had when you were there, or the people you spent time with there.
People get emotional over a car, over a house, over a pet... you could argue for everything it's just a car/house/pet... you can get a new one.
This is more than a SaaS, for you and the others. Stating kind of the obvious: without it Vagrant, Terraform and heck, even Hashicorp would have not been the same - or probably even existed. Despite probably being a later user of GitHub I share the same feelings. It's so sad to see GitHub, a product and company I once respected a lot, getting trashed by Microsoft and all of these outages.
We all understand that. We had some piece of software we still cling on to it (in my case is a copy of paint shop pro 5, corel draw 7 and Delphi 7), despite being completely obsoleted or assassinated by "big industry". I could add CoolEdit 2000 to it, but havent really opened it in a decade.
To be honest, I never understood the fascination with github. Its a hub, of git repos. Not to piss on your parade, because your complaints are valid, but maybe isnt github that as gone sour as much as you have grown out of it. This was your passion, now its over and you move on.
I don't think it is dramatic. I felt a similar sadness around this subject. It's the meaning behind it: the hacker spirit, the naive curiosity, the juveline freedom, being destroyed by the corporate machine. It is a small metaphor that hits all of us in different spots.
And I think that you and GitHub went through the stages of life together. They probably weren't exactly parallel, but I bet you measure and remember your life through GitHub's life to some degree, along with the projects you had there.
There's no question that with your drive and acumen that you could build the GitHub that you both had and want. It might be your next chapter.
I felt pangs of emotion reading the post so it’s definitely not just you.
I think because GitHub has been such an important part of my life dating back to the very start of my career - just like you.
And it’s not just the technology, it’s the people. All the great projects there. The countless README’s I’ve dissected trying to setup something new. There’s people behind all of that and that always felt exceptionally meaningful to me.
It has been profoundly emotional to watch GitHub degrade over the past year. It’s almost like watching someone you love slip away. Which I have also done. It’s not the same, but there is something familiar in the pain.
Meanwhile streamers dunk on it in YouTube videos and on X and none of it is funny to me. It’s just tragic.
I'm sure others have probably said this, but I'll say it anyways. Give Gitea a try. This is what I do. I self-host all my projects and mirror them to Github if they are public projects. And I have distributed Gitea runners across my various servers and they just work and my pipelines never fail me. I'd also highly recommend GitLab CE for similar reasons. But, if you really don't want to self-host, GitLab proper is also awesome and way better than GitHub IMO.
I'm a bit lost about the problem. Is it really about crying about outages? I'm aware of enshittification issues in the broader tech field but the post and this comment don't really say what the problem is. If this is supposed to be some kind of signal and wakeup call, more info would help. For context I'm a lightweight Github user for over a decade, mostly putting up personal projects without much collab, and opening issues in other repos when I find bugs, just cloning and forking stuff (mainly in the machine learning community, but also in general Linux tools). For me it works okay enough, compared with the overall landscape of SaaS. I'm not a fan, don't feel any loyalty and my expectations for user abuse from big tech are admittedly pretty abysmal by now. I'm just not seeing what specifically happened with github to trigger this.
I find the decline of these things upsetting too. I don't know if it slots into enshittification specifically, but there's a phenomenon of decline in general that's so antithetical to where my career began and what I thought was possible. I want to believe we can do better, and ideals can still matter in software.
And I mean, they clearly can; your own contributions are proof of that. We can all do better and the decline isn't a prescription we all need to follow. Regardless, it's tough to watch. Github used to be such an exciting and promising platform.
Wow, thanks for your honesty here. I'm commenting primarily to commend your decision-making which I couch in empathetic understanding.
I saw your post and immediately thought, "good, surprised it took {any organization leaving github} this long." I don't hate big M nor the 'github ecosystem' (except maybe github actions, which seems to get 10x the attention it deserves); the challenge is I perceive far better solutions to be chosen which would serve the open source world if we simply deploy a slight increase in cognitive energy.
Whoever makes fun of you over it is exactly the people you want to avoid.
Leaving any emotions aside, all the arguments you gave are technical and carry weight: we are not always in the mood for OSS work -- or even have the time and energy, which happens to be the much more oft limitation -- and when we are, we want our infra to just work. If it does not, that might kill your motivation for a week. Or a month.
For an OSS contributor, the main one even, this is actually bad news. You are doing both yourself and your community a big service by making this difficult decision.
I think people today think that compartmentalization is easy but sometimes in life your work and personal life and everything else gets all mixed up and you get situations where others might call it unhealthy but for you, it’s fine ante it’s how you want to live your life.
That’s just to say that crying over GitHub is fine, you’re a human, we cry over all sorts of stuff. Emotions are weird and you should not feel badly for having them.
It's a fair writeup and your thoughts are valid. Businesses have to continue to re-earn customer trust each year - especially when it's mission critical and they expect recurring revenue. I hope they find their way too.
If you're still considering vendors, I think you'll find some of the keep it simple ethos can still be found among OSS friendly vendors -- Codeberg, etc. Good quality & uptime doesn't have to be expensive - just grounded by people that care enough to reject the scope creep and focus on doing one thing well.
"Lately, I've been very publicly critical of GitHub. I've been mean about it. I've been angry about it. I've hurt people's feelings. I've been lashing out. Because GitHub is failing me, every single day, and it is personal. It is irrationally personal. I love GitHub more than a person should love a thing, and I'm mad at it. I'm sorry about the hurt feelings to the people working on it."
It's good to care about these choices. There are also lots of ethical reasons to leave GitHub, and this makes it easier for people to choose to leave on those grounds, too. Every time people talk about their decisions and normalize anything that's not just having a monoculture where there are no competitive markets and monopolists control entire ecosystems, that's a good thing.
Do you think this is endemic to large software organizations today, or are our needs (and the corresponding complexity) just outstripping the ability of old business models to address it?
People who reach outlier-level success in a field tend to have strong opinions and an emotional connection to said field. It’s probably a non-trivial part of why they are so successful.
No man, I'm with you. I remember when GitHub was a joy to use. Finding new niche tools and projects written by people who actually cared about their work. Needed some simple postgres backup script? Browser GitHub and plenty of people put time and effort in creating something that actually worked.
I was talking about the same thing just yesterday. GitHub with its friendly mascot is no longer. It's now just another SaaS platform that everyone including my non technical colleagues are using. Their push towards everything-AI is the exact opposite of what they stood for in the begining. A community of like minded people who wanted to build great tools and loved software. But yet no longer. GitHub now feels like a soulless SaaS that's trying to hook my onto an enterprise subscription and bring my whole team along so we can all do some agentic coding or whatever.
You really, really do. Please, for your own benefit, take a step back and touch grass, literally. There is so much more to this world than Github of all things.
> Every day, multiple times per day, for over 18 years... During my honeymoon while my wife is still asleep? Yeah, GitHub
So far everything is going according to the plan. Humans are really close to make the AI that will replace them and enter into the next phase of the plan.
Or do you have a better idea of what the plan exactly is?
In a reductive sense, yeah it's a bit silly. But zooming out, I can understand. Sucks to have your hand forced. Sucks to be let down. Sucks to watch something that was great fall from grace.
Thanks for Ghostty, been my daily driver for awhile now. Hope the rest of your day/week goes much better!
Bud. Right decision. Time is a forward moving arrow. You gotta do what's right for the project and over the years I've rarely seen your decisions going against the stream.
> Its given me so much and I'm so thankful for it. But, it's not what it used to be. I don't know.
Mitchell, when I was in 10th grade and had to pick my streams which led me to pick comp-sci/stem rather than finance (I am going to college soon), I thought of my dream life and it was being on a vacation/beach using Linux or terminals and opening github and contributing to open source software. I simply couldn't imagine my life without terminal (funny because ghostty is the terminal that I use)
You said that you have been with Github for 18 years, that is longer than the time I have been on earth. You were (and in some sense are!) living my dream life in that sense and github fulfilled its role, it had helped you until recently when it has started to get worse and worse.
my point is you have an special bond with github and for good reason,so to remove an somewhat integral part of all of this (github) after so long will have emotional feelings and outbursts.
I hope that you are doing fine, Ghostty/your-work has a positive impact on my life and gives a hope by being a relaible tool I rely on, I wish nothing but the best for Ghostty and you personally.
Hey bud, thanks for the honesty and I feel your pain! You're an incredible engineer and I've looked up to you (even though we are the same age) since hanging out at Kiip. Our tools should be getting better not worse. Hopefully your influence can be a canary in the coal mine to make some real change to reliability. -D
It's not a stupid thing - GitHub not being serious about basic reliability is, at this point, a big risk to people depending on it for change management, much less OSS projects needing it to do every aspect of work in the public.
GitHub made working in the open a joy. It's very sad the state that it's in.
> GitHub only gets better if people who give a shit stick around to make it better
Quote the opposite. We need to leave so they receive the message in order to fix it. As far as the suits know, life is swell. So much so they can't keep up with demand. Be sure to say why you are leaving too, so they know what to fix.
No serious person would make fun of this emotional reaction. It seems technology had something going on, and it quickly got flooded by incompetence and greed.
We have all been deeply involved, constructed careers and sharpened our tools with technology and hopefully for the benefit of technology.
I can only imagine how deeply sad the current state of software is for those talented individuals that helped to carry it to here.
Some of us can at least hide it with cynicism because there is not much at stake, but emotional honesty is very much appreciated.
Damn GitHub is at a new low. I wish GitHub wasn't overtaken by the AI agents and hoped that the situation would improve. But it just didn't and ever since Microsoft took it over, it was just run into the ground.
I thought that GitHub was so unreliable that it would be better to self host instead of use the service [0]. It turns out that 6 years later, that was the case and it doesn't sound crazy anymore.
The problem is GitHub was neglected and the AI agents ran it into the ground and we need to now self host.
Github won't shed a single tear in return, hell, they probably didn't even know until this came out. And not to sound harsh, but they probably don't care either. If they don't 'find their way', then there are 10 different competitors ready to take over, and I hope some of them do. Better for the ecosystem to have a strong element of competition. Perhaps their time as top dog is ending, and it's only natural, nothing lasts forever, especially in tech.
You have been a tremendous influence on my professional life. Vagrant made VMs easy to use. You were very gentle with my Vagrant PRs. We disagreed a bit and I migrated some of those rejected Vagrant PRs into VeeWee. Then Hashicorp happened and I was over the moon. (Full transparency - not everything was perfect, I lost 50% of my Hashicorp equity which hurt real bad but that's not your fault, just saying there were ups and downs!)
This is all to say I have tremendous respect for you. Which is why I say:
You also have the resources to fix this. You not only have the resources and skill Mitchell, to make it happen - You know everything that it takes to be the CEO of a Billion dollar unicorn - you have the connections, you have the vision.
More importantly, Mitchell, you care.
Make it happen. You have done it a few times before. Do it again.
Tools can be frustrating. We can get emotional with tools we appreciate and we grew up with. But we should also learn to not focus solely on work efficiency. As you say yourself, this is unhealthy. You've labeled it, now work on fixing that unhealthy relationship with work, and with that tool.
Nobody should be in an emotional turmoil because they can't do a PR in a 2h window during a day.
We should all learn to take things more slowly, because our current accelerationist society is detroying the planet, and is destroying social ties.
Because, if you get that emotional from on a non-functioning tool... wait until you discover how our non-functioning democracies allowed for a genocide to happen in Gaza, for people in the south to be doing slave-work for our AIs to satifsy people in the north, etc
It really has been remarkable watching GitHub just crumble as an organization. There's a lot of discussion about why: the switch from being independent to being part of Microsoft, having resources pushed to Copilot instead of core service, the organization structure itself, a reliance on vibe coding, etc etc.
Regardless of the reason, it's undeniable that GitHub is facing some serious issues. The unofficial status page[1] tells a horrifying story.
I would absolutely love to get some insider perspective on this (if only to learn how to prevent it from happening anywhere I work), but I think it's clear to anyone who has been paying any attention that GitHub is a sinking ship and the only reason people haven't abandoned it already is inertia. Considering how much else is changing in software right now I don't think inertia is enough to sustain a company.
I do not work at MSFT but I don't feel that I need insider perspective to understand what's going on. GitHub is being managed the way other services get managed once they're bought by big companies. Initially fine, then starts to decline, then eventually craters. Everything becomes the numbers game.
Microsoft, Oracle, VMware, CA (where software goes to die), Salesforce, the list goes on. Every once in a great while there's a good M&A team that doesn't fuck it up but that's sadly rare.
I feel like MS went out of its way to make a point that GitHub and NPM would be independent orgs that no longer had to worry about making keep-the-lights-on money. It was positioned as a benevolent acquisition for the good of the development community.
As so often happens, that didn't last long.
Nest was originally independent. Didn't take long for it to merge with the Google Home brand.
I'm afraid this is a form of reversion to the mean. Successful startups are made of exceptional people: the founders, the initial investors, the first employees, the first clients. But when they get acquired by much larger companies, they are necessarily diluted in pool of people that are more "normal", less exceptional. This includes the customer base that is more "normal" as well. Slowly but surely, the extraordinary product/service the startup has been developing reverts to the mean. This is quite sad, because it feels inevitable. I'd like to know how to avoid it.
This is a general observation, no hard data, but I find there seems to be a wall at 2 years after an acquisition. By 2 years a lot of the best talent leave the company entirely or go somewhere else in the company. Things can cruise along just fine for a bit, but as the institutional knowledge slowly leaves it gets worse and worse. Couple that with the bureaucracy and insanity of a global mega-corporation, the quality fades slowly at first, then it picks up.
> GitHub is being managed the way other services get managed once they're bought by big companies. Initially fine, then starts to decline, then eventually craters
Can you explain what you mean by this? Like what does "fine" mean? What, specifically in the management, is the "decline"? What does "craters" mean?
In their defense, they dramatically "over"-report sev-2/3's (things like, avatar urls are not loading in saudi arabia), which makes their cumulative uptime look much worse than it is.
If you filter for major/critical outages, their uptime of core services in trailing 12 months all have two 9's.
Also, a huge part of their cumulatively-bad availability story is copilot, which is a functionality (LLM inference) that most organizations have struggled to get two 9's of availability in for the last 9 months.
Some years ago I wondered how long will it take them to go they way sourceforge went. Once you grow too much without a proper leader, you will fall :(.
Sourceforge died in a very different way though. Bundling spyware/crapware in install packages for open source software was a serious breach of trust, and was pretty much the direct reason for mass migration to Github. Github is failing on the technical side, but they at least mostly have their brand value intact. I think it will still take quite a lot for a mass migration of the same scale to happen.
Comparing GitHub and SourceForge as if they were cut from the same cloth is laughable to me. SF has always been a wretched hive of ads and dark patterns.
I think that is exaggerating things a bit... GitHub is alive and well, and they're hosting more and more projects each month. A few well-known projects leaving every now and then doesn't exactly spell doom for GitHub
Have those outages actually been blocking your work? Somehow I haven't even noticed, just seen complaints on HN. I'm not saying it's not real, just wondering where the gap is.
Yes, many times. Roughly once a week this year my team or an associated team can't ship changes because PRs, GitHub Actions, or some other associated mechanism is down.
A big part of my job is doing code reviews, and its very common that pages or diffs just don't load. Or PRs literally don't appear in the PR list, even though they exist. It's a daily occurrence to play the 'is my internet down or is GitHub just being shit again?' game.
Oh, and don't forget the cases where the diff view sometimes misses some files for unknown reasons. Both in the 'new experience' and the 'legacy view'. You just can't trust it as much anymore.
So what? People have to unlearn this kind of brand loyalty. Companies are not people and not your friends. They are in the business of making money. We need to be more aloof and simply use their tools when useful and not get emotionally attached. Most of the managers and likely the devs had a good deal. Good money, and if it collapses, people still have a good resume line and can move on. And we users can also move on. There are plenty of other service providers of code hosting and CI/CD.
All of that is revisionist history at best. GitHub was a pile a shit long before Microsoft bought it has everyone forgotten when it would be a coin-flip on any given day if the site was even functional?
GitHub was in the right place at the right time to be a success despite the fact it's a massively clobbered together mess.
While I wouldn't necessarily phrase it this way, there is a chart going around social media that tries to imply that GitHub had basically 100% uptime right up until the MS acquisition. All it takes is either 1) having been there or 2) a cursory search of HN to know that this is a complete fabrication.
Hm. I read that as saying that their users are writing more code with the assistance of LLMs, thus placing more stress on their systems. I do not read it as making any comment about their own practices.
Even if you go service by service you're talking about critical things like `git` operations (literally what they're named for) at a single nine, and stuff that's pretty basic like static web hosting as only two nines. They literally can't even keep static webpages up.
I can appreciate Hashimoto's genuine feelings about Github, and the world of open-source software development that it opened for him and that he spent a significant chunk of his life participating in.
On the other hand, I can't help but think that some of this heartbreak would have been avoidable, if only he possessed more of the Richard-Stallman-esque attitude that non-free software is inherently suspect and unethical. Github has always been non-free software hosted by someone else, and run according to its owners' rules and for its owners' benefit, not ultimately the end user. This was true in 2008 and it's true today.
I've also used Github for a significant chunk of my life, often because I had to for my job. But I've never developed an emotional attachment to it. Indeed, I have long been annoyed that Github is someone else's proprietary software, that does what it can to structurally lock users into their platform despite being built upon free-software git.
I've never been able to love software that requires an email-based account and accepting terms of service and that doesn't work in Iran because the company that runs it obeys US sanctions law.
So without reservation on my end, I'm glad to see that ghostty is moving off of github to something else.
> Github has always been non-free software hosted by someone else, and run according to its owners' rules and for its owners' benefit, not ultimately the end user. This was true in 2008 and it's true today.
Yup. At KDE we never seriously considered GitHub. We always built our own git infra, and eventually landed on GitLab, after banding together with Gnome and a (generous and forthcoming) GitLab to convince them to move everything we needed from the Enterprise Edition to the free software Community edition.
I think we've had exactly one multi-hour git outage in 16 years.
The centrality of GitHub was part of its appeal. It’s where you went to see where nearly every (obviously not all) open source project was being developed. Based on his post, the network effect was a large part of the draw and the reason he stayed despite reliability issues. A more federated set of git UIs will never capture the same feeling.
I made the decision to leave Github a couple months ago when I retired and started heavily working on personal projects. I like the idea of radicle and used it for a while, but it's complicated to set up and maintain if you want to run your own seed node and pin your personal projects.
What I ended up with is a version of a static forge - Charm's soft-serve to host the repos and a forked version of the pico.sh pgit static site generator. I added git-bug integration to track issues in the repo and an alternative CLI to git-bug that works better when collaborating with agents.
A static forge site is very resilient to bot traffic because it only renders a limited number of commits, instead of pathologically allowing a near infinite number of URLs for bots to crawl.
Exactly this. Even though I don't use git-bug anymore, I'm still a sponsor. I desperately want an issue-tracker-in-.git to become a standard.
Issues and CI are the only lock-in. The latter is legitimate because you're using someone else's CPU, but every developer has the tooling to "git diff" and write comments if we could just agree on a format.
They're all just value propositions. Is it worth my time and money? There ya go that's it.
It's not unlike the emotional drama I see each time Netflix raises prices (people get really upset about that), or video game discussion (the worst). If it's not worth the the value proposition, move on ... don't hang on / waste emotional cycles on Netflix or something like that ...
Granted I'm not a robot, I get the the emotional connection too, I think back to my early days in computing and I still fondly think of the now defunct manufacturer of my first PC, later the Windows 95 start me up commercials ... it was something magical.
The thing you love has been bought by Microsoft. When things belong to a large corporation, they can (and probably will) drift off in some absurd direction, because in a way, the relationship is reversed. The thing no longer serves you; instead, the brand, the user base, the reputation, and the key role and function of the thing are put at the service of investors. In this process, you are demoted from subject to object; from an animal grazing on open grasslands to an animal grazing in a fenced-in pasture to an animal standing in a stall and being fed compressed pellets that contain bone meal from its own species for nutritional value. That’s why it’s important not to walk into the fences too naively, even if the grass there is fresh and lush.
During one of the x threads where Mitchell was (legitimately) complaining about Github, there were a couple replies suggesting that GitHub should hire him to be their CEO.
And I remember seeing that and thinking "huh... not at all a bad idea."
There is a specific kind of leader that can turn such ships around, and they are strong in their convictions, and aren't just "managers", but visionaries coupled with strong execution and power to attract talent.
I think a new GitHub will emerge and when it's just right, will grow like wildfire (like OpenClaw, or even GitHub itself did during the SVN and SourceForge era). And many are already trying to be that new GitHub.
Every time Fossil comes up, people's big objection is that you can't squash commits. Personally, I'm fine with that - I tend to agree with Hipp that the repo history should not sacrifice truth for the sake of pettiness in the timeline. But a lot of people seem to disagree, which limits the audience for Fossil. I use Fossil for my own projects but I wouldn't expect it to become big like git is.
The problem is that what users want GitHub to be and what their owners (Microsoft) want them to be are disjoint.
If AI replaces software development the way that big tech company management wants it to, maybe they'll converge again. In the mean time, people want a git remote and they're getting an unstable host diluted with some flaky vibecoding bullshit.
He would pull them away from co-pilot and the unlimited spigot of money that agentic coding brings, which is contrary to the best interests of Microsfot.
I'm still holding out hope for distributed and federated git forges. The only compelling reason for everyone to centralize on GitHub is collaboration on issues/PRs without everyone allowing signups on their self-hosted forges. That could be achieved without hosting every line of code everyone's ever written in the same crumbling infrastructure.
It'll probably never happen. But it'd be really nice if it did.
> I'm still holding out hope for distributed and federated git forges.
Do you know that you can just send a patch via email (assuming you're not using the gmail web client)? You can even save the diff on some hosting website and send the link via any text medium.
> I think a new GitHub will emerge and when it's just right, will grow like wildfire (like OpenClaw, or even GitHub itself did during the SVN and SourceForge era). And many are already trying to be that new GitHub.
Really? I can only think of two: Codeberg and Sourceforge. Which are both great, but that's not what I'd call "many".
Aside from outages, what really bothers me lately about GH is how slow the "app" actually is. Keeping a tab open on a PR status check burns 25-30% of a core on my cpu even when it's hidden. Reviewing large PRs has an awful workflow. Almost every diff page I load starts with "there's nothing here" then starts to load...
>It’s not a fun place for me to be anymore. I want to be there but it doesn't want me to be there. I want to get work done and it doesn't want me to get work done. I want to ship software and it doesn't want me to ship software.
Has anyone else shared this sentiment? If so Redmond needs to lean in hard.
this is an absolute killing blow for Microsoft if it gains real traction. You made developers your cornerstone eight years ago for nearly 8 billion dollars. you spent another 2bn on minecraft to clinch the deal with young developers and the code camp kids.
Youve lost the OS, and the server realm. Lose the developers, and youre on your way to becoming the Xerox of the 21st century.
> Youve lost the OS, and the server realm. Lose the developers, and youre on your way to becoming the Xerox of the 21st century.
This is a very HN take. MS is terrible or at best "second tier" on everything they do including gaming, they also lost the mobile race, they're very likely going to lose the AI race, but they'll still hold hostage of the vast swathes of average white collar workers with Office, people that don't care at all about technology as long as they have Word and Excel.
There's a reason why writing .docx was one of the first proper skills that Claude got.
It's something that Microsoft leadership themselves certainly seems to have believed at times. From "developers, developers, developers, developers!" to courting Linux-targeting webdevs with WSL to VSCode, they've done lots to court developers, sometimes explicitly professing it as a central part of their strategy.
I can't disagree with any of the rest, though. Microsoft's (anti-)competitive strategy has never been about excellence so much as positioning worse stuff to win in virtue of network effects and integrations.
> but they'll still hold hostage of the vast swathes of average white collar workers with Office, people that don't care at all about technology as long as they have Word and Excel.
I can't wait for the anti-trust lawsuits. M365 and O365 are already super shady in terms of being able to migrate out or be interoperable with other solutions. "Accidental" roadblocks almost everywhere.
People have been saying that MS was becoming obsolete for at least two decades. And a few times, it did seem heading to obsoletion: first when Google Docs launched, and second when Windows Phone failed.
And yet we're where we are. MS is still one of the most important corporations. Perhaps the most important one if you only count enterprise usage.
FWIW I also think an underappreciated advantage is Windows Server (last I checked that was still rock-solid) and Active Directory. Lots of CIOs / CTOs would correctly veto a move off of these, absent a specific technical problem. This is really more of a "hard knocks" lesson than anything fundamental to operating system design or implementation, but: the two Linux shops I worked at got at least a little sloppy about the sudoers list, or got frustrated and gave too much access to a "shared" folder, etc etc, largely because the admins got fed up with all the Mother May-I-ing. It just seemed to inevitably turn into a mess; sometimes that mess is fun and even productive, sometimes it's actually unacceptable.
Even the research hospital I worked at had a proper SELinux setup on the Red Hat installations, but by-quantity most servers were CentOS and it was way more of a free-for-all than it should have been, e.g. I was the fed-up admin when I was really not qualified! I screwed up a lot. Not that big of a deal: this was research-related computing and deidentified data. All the clinical computing was Windows Server. That is not a coincidence, it is really a market difference.
As someone who hates Windows 11... I do like the core Windows kernel, and would much rather do IT on Windows machines than Linux machines. Windows NT is very fussy and a bit bloated, but a huge part of that is an admirable commitment to backwards compatibility; a lot of XP applications run fine on Windows 11, except DPI wonkiness. And Windows' driers advantage isn't just commercial support; the kernel is fundamentally leaner and faster than Linux at real-time IO, and better about cleanly isolating driver processes across privilege levels. Very broadly, compared to Linux I find administering Windows easier to navigate and harder to screw up, especially with handling user permissions. Surely part of this is what I grew up with, but there's also a values difference: a lot of Linux users like how low-friction it can be since the OS doesn't get in your way. I kind of like that Windows makes you turn an excessive number of disarming keys... even when I am frustrated by it.
It does make me quite sad that the only real general-use OS options are the apex of a 20th-century operating system family, Apple's version of that, and a truly 21st-century monolith-microkernel hybrid whose specific design is a mystery to public science.
> you spent another 2bn on minecraft to clinch the deal with young developers and the code camp kids
You think? They're still pushing the "native" Minecraft that isn't scriptable aren't they? And maintaining the fully moddable java MC against their will.
Nope. I think all this is mostly virtue signaling and a bit of "GitHub derangement syndrome" in the water.
People are ANGRY about the AI boom impact right now and "microslop" is trending harder than "M$" back in the day.
MH had a weird ass set of Tweets a month or so ago talking about GitHub needing disruption and how the UI was bad. Now it's "Not fun anymore".
I guess you die a hero or live long enough to be irrelevant and shouting at clouds like Stallman.
Work at a company on GH Enterprise. Outside those recent major incidents and a few spots here and there we haven't even noticed issues. It NEVER comes up on engineering or leadership meetings as an issue or risk. Not a single time has GitHubs issues come up as an agenda item. Yeah, YMMV but still...
> People are ANGRY about the AI boom impact right now and "microslop" is trending harder than "M$" back in the day.
The writer of this blog post is Mitchell Hashimoto, and he has posted positively about AI, so that doesn't track at all.
The reason people are talking about it is because the decline is rapid. That's worse than the raw downtime. There's a sense that it will be even worse in a year.
I'm not a fan of AI everywhere but I have 0 reason to think this is from AI usage at Microsoft. Still, we talk about the issues a lot. We used to do our project management in GitHub. For whatever reason, projects don't work anymore. You can add an issue to a project and it won't show up. So we moved that part off of GitHub. That's too bad, I liked linking to issues.
If this happens enough, the only thing left will be hosting code, and we'll look at each other and go "we can do this anywhere"
> To the "Git is distributed!" crowd: the issue isn't Git, it's the infrastructure we rely on around it: issues, PRs, Actions, etc.
A suggestion: use git-bug https://github.com/git-bug/git-bug in addition to migrating to another forge like Codeberg. It saves issues, PRs etc in git itself (not on a branch - on a specially crafted ref). It offers two way sync with a lot of providers.
Other VCSes like fossil store issues alongside the repo. I think it's appropriate because in a sense, issues are part of what gives meaning to the code (like documentation)
git-bug is great but it doesn't handle PRs nor does it have a method for users without commit rights to submit bugs to the project. I know they're working on the latter (something with the web UI?) but until then you still need some kind of public infra for issue management if you want the general public to be able to submit issues.
I use it for my project[0] to keep issues centralized with the repo, but I still use Github Discussions as a pseudo-bug tracker to let random users provide input. If it's a bug I add it to git-bug and sync it to Github issues for public viewing[1], but if you want use bug reports that's not really going to work.
[1] Ironically I got this workflow idea from ghostty and mise, both of which require users to submit bug reports as discussions first and only generate tagged issues once an actionable bug is determined.
Maybe Mitchell will pull a Linus and, out of frustration, take a weekend off to write the distributed infrastructure for issues, PRs, actions, etc. around git.
The most important part of Linus' project was day -1, when he sliced off all the chunks of work that depend on solving open research problems.
You don't want to start your Saturday morning declaring an _action struct, then filling the rest of the day staring at research papers about the current state of fast homomorphic encryption.
> Other VCSes like fossil store issues alongside the repo. I think it's appropriate because in a sense, issues are part of what gives meaning to the code (like documentation)
I was thinking about fossil in the context of agentic workflows the other day, after seeing a co-worker go all in on sort of shifting themselves to a TPM workflow, using a locally hosted kanban board (inspired by OpenAI's Symphony).
It'd make things easier to have everything shoved into the repo, other than that everything is now shoved in the same repo being handled by the barely constrained chaos monkey that is an LLM coding agent. Locking things down gets hard if it's got access to the whole thing there.
> Other VCSes like fossil store issues alongside the repo.
Technically the issues in Fossil are part of the repository, along with the wiki, code, forum, etc. They come along with every clone and (mostly) cannot be deleted from the historical record.
Items of Fossil that are merely "alongside" instead of actually in the repository include unversioned files, chatroom content, and users and access controls. (Not an exhaustive list.)
It's definitely time to turn these loose web features into a real program. I don't understand the desire to clone github as a website. It's demonstrably 10,000x more work to maintain github.com than a "github" command.
We've had trouble with git and repo's that have used non standard refs. It's all fine and fancy until we wanted to use some tooling that works with git, except it wouldn't see our unusual refs, and because they were non standard they were effectively hidden unless you knew they were there. So the migration work (almost) silently lost 10+ years of old work that was hiding away under those non standard refs.
Coupled with this (unsubstantiated but thorough) discussion on the internals of Azure, if even a fraction of this below-linked post is true, Github's abnormally-filesystem-intensive workflows would have wildly unpredictable performance and reliability forced onto Azure.
Azure also regularly has incidents due to capacity issues in several regions, so that many Azure-managed services also go down. Some of those incidents have been open continuously for many months now.
Well, it started just after the Microsoft acquisition, when AI did not exist, and coincided with news of Microsoft fully ingesting the GitHub team and forcing architecture and priority changes, and has steadily continued since. So idk, it’s a mystery. Maybe it was caused by the thing that did not exist when it happened. Microsoft just posted on a PR blog that it’s the thing that did not exist, and they’re famously truthful, open, and altruistic.
It's been on a downward trend before agentic coding took over. I suspect it's a mix of Microsoft culture and Microsoft infrastructure. It's starting to feel about the same quality as other Microsoft services.
Short aside, I have to rehost dotnet CLI binaries because their hosting infrastructure is so unreliable that it was causing CI failures regularly.
It began pretty much immediately after the acquisition. There was an uptime chart making the rounds a while back, and less than a year in, the all green data points of pre-Microsoft Github turned to lots of red. I assume brain drain, as everyone vested or otherwise completed their contractual requirements and cashed out. And, Microsoft has never had a great reliability culture in their cloud services, so no in-house talent to effectively take over.
Incomplete pull request results in repositoriesSubscribe
Update - We are actively reindexing the remaining ElasticSearch indexes. Our priority is ensuring correctness and avoiding further impact. We are taking a measured approach to safely backfill data and will share additional updates as progress continues.
Apr 28, 2026 - 15:58 UTC
Update - After yesterday’s incident, we are investigating cases where /pulls and /repo/pulls pages are not showing all indexed pull requests. This is because our Elasticsearch cluster does not currently contain all indexed documents.
No pull request data has been lost. As pull requests are updated, they will be reindexed. We are also working on accelerating a full reindex so these pages return complete results again.
Apr 28, 2026 - 14:51 UTC
Investigating - We are investigating reports of degraded performance for Pull Requests
Apr 28, 2026 - 14:17 UTC
#2 makes #1 a big problem. AI-generated code is fine if you have thorough engineering practices around it. Are they blindly merging in AI generated code without review? Maybe. Thats an issue of engineering practices, not of the use of generative AI in general.
GitHub took a massive hit in credibility when it got bought by Microsoft. We are a burned generation, we have seen the worst of Microsoft. This created a massive crack in the foundation of trust for most people.
Then Copilot happened. Some people dug how the training is done, and one GitHub employee responded by mail that every public repository including GPL repositories are included (the relevant Tweets are deleted unfortunately). The created crack has deepened. Some of us (incl. me) left GitHub.
As Copilot entrenched, Microsoft's product development practices and philosophy took over, and vibe coding started to be used by hordes of developers, GitHub's code foundations started to crumble. Add the big migrations they're doing & regressions they are causing on the UI now, and we're here.
GitHub's first enshittification cycle is over. Now we're starting the second cycle. The bloated, slow, entrenched hegemon's decay from relevance phase.
It'll be a slow decay. It won't fall in a day, but they golden era is long gone.
Any more context on the copilot training note? More pointers would be very interesting, but we'd need to keep in mind how many different underlying models were (are?) branded as copilot. I thought at some points the "copilot" model in autocomplete contexts was a finetuned GPT from OAI.
Re: GPL, there are other open access datasets of git repos that make some distinctions between copyleft licenses but those are older resources now.
Azure is not the best, but it mostly works. GitHub gets only 98% reliability for git operation component, reading and committing. This is the most basic component. The fact they are not on this 24/7 and it isn't fixed is the result of a culture (=what is prioritized, what quality is accepted).
Reading the write-up again, this really struck me:
It’s not a fun place for me to be anymore. I want to be there but it doesn't want me to be there. I want to get work done and it doesn't want me to get work done. I want to ship software and it doesn't want me to ship software.
Github is really Microsoft. The above paragraph captures perfectly what it's like to work in a big company like Microsoft.
When Github was a startup, it was both a tech company and a social media for coders and a real-life social scene (especially in SF, some pretty epic stories over the years).
Once Github was acquired, it was a countdown to all the soul being sucked out of it and simply a mechanism being left behind.
I'm happy that raw git + mailing lists works great for the linux project, but can the rest of us all agree we actually do need issues & PRs? And that it's super painful to lose all this context when platform hopping, or when the service unilaterally decides to deplatform someone?
So where are we going? Mitchell will be deciding for Ghostty. If github's current trajectory is anything to go by, everyone else will need to decide where to go sooner rather than later.
I'm worried that it will be a Babel scattering event and this open source superpower that github catalyzed (how to describe it?) will just evaporate.
I'm also worried that wherever we go next could have the same fate as github.
So what then? Radicle is the only thing that I've seen that could theoretically 'solve' the problem, though it still needs a lot of work: https://radicle.dev/
There will be disruption as people move to various platforms and then one will “win” by a small amount which will self reenforce until we have a new GH and the pattern will likely repeat.
Companies will keep using GH for a long time because they seem to be really tolerant of outages (and have a massive switching cost depending on how much of GitHub they use outside of git).
Smaller teams/solo devs much less so.
Isn’t really anyway to coordinate it ahead of time, it’s more an emergent bottom up thing than a “all devs agree to move to X” ahead of time.
Radicle stores issue & PR data as git objects. This approach interests me because issue data is as important as the code so we should treat it with the same care as the code. I.e. a tamper-proof cryptographic chain, signed objects, distributed redundancy, well-tread management features like synchronization and packfiles, etc.
> I know I work at GitHub so that might sound heretical, but I promise it’s not controversial for me to say it. Very few people internally believe that PRs and issues are ideal primitives for the future of engineering. And there are a lots of us inside the machine exploring what comes next.
Honestly the arrogance of their workers are truly astounding. It also tracks that someone with little software experience would become GitHub's staff research engineer. Truly a massive signal that we can't let these companies lead the direction of tech in our country.
I’m Maggie and I’m a staff research engineer at GitHub Next. At least that’s my title, but I’m actually a designer. Or I was, back when that was still a separate thing to engineering.
Ah. I didn't think we could debase the title of "engineer" any further, and yet here we are.
The state of HN truly has fallen if people are questioning Maggie Appleton's credentials. Besides, she's working on GitHub Next, not the core product. Sheesh.
You weren't kidding. They're an anthropologist who went into design a few years ago because "it's not terribly employable" and as of less than 1 year ago was a "Lead Design Engineer at Normally"? This is GitHub Staff eng steering the direction of the concept of PRs?
Github released that split PR beta, so sounds like they are still thinking about the future which is moving towards small manageable PRs which are part of a parent ticket. That's a solid way to dealing with AI codegen bloat.
The arrogance of anybody, let alone a designer, thinking they could build something better than the foundations of software (and the modern world itself) is crazy.
I love it, but you have to deliver or else I will mock you :P
I'm very interested in where ghostty ends up - I wonder if they'll follow Zig to Codeberg?
It does seem like it might, in general, be a very opportune time for GitLab (or another host) to publicly step up!
There seems to be a lot of chatter on X recently about wanting an entirely new GitHub usurper that doesn't look like GitHub at all, but in the short- to medium-term I expect this not to gain a huge amount of traction because of the sheer cultural embeddedness of git + GitHub in modern day software development.
Would love to see it become more common for projects with sufficient inertia to host their own forge like GNOME or Inkscape do. Could be a service that foundations like CNCF or LF offer to their projects.
GitLab? We use gitlab for work. Its way worse in comparison.
Last week I encountered a bug where my merge request simply didn't show that I deleted a file. Apparently it's because my MR included the creation of a folder with the same name as the basename of the deleted file. Unacceptable for a code hosting platform.
Other than that I miss GH Actions, a clear ui (gitlab has way too many sub-menus), a responsive ui (gitlab feels very sluggish). And while we don't have the Gitlab duo activated, it still pops out regularly eventhough I can't use it besides closing it.
...and I don't even want to start with their issue buard.
It strongly reminds me of Jira in terms of quality, which is no compliment.
This seems like a great opportunity for new platforms who are rethinking the OSS space to finally gain the traction they need to be effective. For a collaborative platform, quantity is key, and I am hopeful that someone who is interested in advancing the software space will become the new go-to. This isn't to say that GitHub hasn't been innovating, but at least from my perspective, the way we've used git for the past however-many-years has remained basically constant.
Some projects that seem interesting:
- https://tangled.org/ seems to be building out cool and exciting ways to write and interact with code (and they're distributed on the ATProto! But notably that's not their core selling point)
- Microservices like https://pico.sh/ and https://sr.ht/ feel like fresh air...
Love sourcehut and want to see them succeed, but their build service (despite having some very cool ideas like allowing you to SSH into your build container) is pretty barebones / lacking compared to GH/GitHub actions. You either get no task parallelism (all your tasks are in one manifest) or you get up to N=4 parallelism (you have four manifests). As far as I can tell, you can’t specify job dependencies beyond just “when this job finishes, trigger this next job by deploying a manifest”. No build caching, and artifact sharing felt like a kludge.
Thanks for the callout: we’ve been reimagining code forges by making them irrelevant with tools and tiny services like: https://pgit.pico.sh (static site generator for git) and https://pr.pico.sh (pastebin for git collab)
They are still a WIP but it’s on our roadmap to continue to improve.
I’d love see Tangled succeed because it strikes a good balance of UX and features. Sadly, there’s no clear pricing story around managed solution. They are also VC funded so they can follow the “journey of VC backed org” anytime.
I don’t know if it’s production ready yet, but tangled.org is a really interesting take on a forge and I’ve been watching it for a while. It decentralizes the centralized parts of GitHub in a pretty neat way. The biggest problem with forges that aren’t GitHub is people need to make and manage all these different accounts for each place they contribute (which almost certainly will lower the amount of people who do. Maybe this is a good thing these days though...)
Tangled uses the identity stuff from atproto which lets the important stuff (git, CI, etc) be decentralized while people only need one identity to contribute (and you can self host your PDS too). So nothing ends up being reliant on a third party.
I'm also closely following Tangled's development. Their two biggest weak points: lack of private repositories and ux design (which I don't have a problem with but I've seen many people mention) are both being worked on. Atproto is developing a permissioned data segment to the protocol, and Tangled just hired a designer. I'm excited for it.
>manage all these different accounts for each place they contribute
For me that's a minor problem. The struggle of working across multiple code forges or making my code available on multiple is syncing CI/CD, issues, releases between them. I don't have the energy to maintain multiple versions of a pipeline.
maybe, but tangled knots actually federate. you could contribute to repos on knot.ghostty.org and knot.tangled.org with the same account. no other platform permits one identity across instances.
With malicious HTTP headers, any user could access any repo on Github.com, or on the Enterprise Github instance they might have access to. It's even worse than that because it's remote code execution on the Github server.
It seems like Github has been a mess since the Microsoft acquisition. Definitely feels like another multi billion dollar screwup in the making, like Skype or Nokia were.
Hopefully the incidents in the last few weeks are a wakeup call, and they start getting their shit together.
Not surprised, I think I was subconsciously waiting for this as Mitchell has been very vocal about Github on X. They killed a lot of developer goodwill, and I feel this is just a start of the mass exodus.
Good luck to the team with migration! (And here's hoping it's ersc :))
I really wish an open-source developer of his caliber would also migrate to a serious microblogging service which isn't so openly hostile to truth and civility. Ending the sticky network effect of an evil service starts with its biggest, most prolific users migrating away.
I find the alternatives more likely to ban/censor than X. Bluesky is definitely not civil to those with the "wrong" opinions, despite what proponents of the service say.
It's not about the technology, it's about the people. The initial people on your network matter. The moderators matter too. That's just a very different job than writing and shipping code.
It's all about who you follow. My feed is mostly AI people, entrepreneurs and nerds. Some political stuff gets through, but otherwise, I'm glad to be back on X in the last few months (I left a few years ago in disgust over the insane politics because even nerds were only talking politics).
I know gitea / forgejo will be a popular suggestion, either self-hosted or via something like Codeberg. Despite also being a GitHub user since 2010 and also "doomscrolling" issues for projects I am involved in, I do host a gitea for personal projects where I don't need the GitHub network effect. It works well and is surprisingly capable!
I migrated my entire workflow onto a personal GitLab instance after the whole "pay a fee to bring your own bags to the grocery store" GitHub Actions pricing shenanigans earlier this year.
Best decision ever.
100% uptime. 100% less stress with each of the product/pricing changes over the past few months.
Was also able to build my own GitHub Copilot equivalent that auto-reviews MRs interactively.
i am opposed to using anything which is not single binary and not using a sqlite db for self hosted things which don't need to scale to millions of users.
Yeah, if you're hosting your own just use forgejo. Forgejo has a better governance model and is actually open source, not a corporate project that happens to advertise in open source. The distinction is meaningful.
I had steered away for a long while thinking it was subpar to GitHub, but it's really come a long way. Especially running it on a local network it's noticeably faster in every way than GitHub, and I'm able to build complex gitlab workflows with custom runners that are fully configurable and have effectively 100% uptime and no queues.
forgejo has been great for us. It scales remarkably far with the built in sqlite db also. Single binary, no deps. You ofc have the option to hook it up to a proper database server.
It’s a rails app from the early 10’s era think heroku dominance. therefore to run it you’ll need a dozen sidecars for things like redis or elasticsearch and others. it has all the fun ergonomics and bloated memory consumption of that stack as well. the all-in-one go based tools are probably better for a solo homelab style deployment (gitea etc)
Is it a joke? GitHub is not perfect, but it is mostly free and survives billions of commits every day. You don’t think We are all able to scale a service so well.
I don’t know, I love it. There are many alternatives like bitbucket, gitlab, but GitHub is still better overall.
What is confusing to me, is as a business I would happily pay GitHub for many many features that I pay others for. Maybe MS thinks its just a billion here, billion there, but isn't it so easy to capture these?
1. faster more configureable action runtimes so I can get faster builds
2. usable merge queues because the github one is a joke
3. some reasonable CI management and workflow debugging features
Founder of WarpBuild here: we provide faster runners (also cheaper), and have some niceties around debugging workflows like ssh-ing into them, observability etc.
It was four years ago that GitHub had major enough outages with their database that they had to issue a press release (https://github.blog/news-insights/company-news/an-update-on-...). Five months ago I was actually still recommending GitHub. Then a month ago I left the platform, because I couldn't get shit done anymore.
The alternatives aren't great. If any VCs wanna send a couple hundred grand my way, I'd be willing to start a GitHub alternative, if only so I could have a not-crappy place to host my own repos.
> When I went through tough breakups? I lost myself in open source... on GitHub. During college at 4 AM when everyone is passed out? Let me get one commit in. During my honeymoon while my wife is still asleep? Yeah, GitHub. It's where I've historically been happiest and wanted to be.
I've never had such an obsession to a platform or an activity as this. Some might say this is unhealthy, but I admire folks who can reach this level of obsession in their craft. It's just a joy to read about for me
Not to defend Github, but I sometimes feel there are two Githubs that aren't related to each other.
> This is no longer a place for serious work if it just blocks you out for hours per day, every day
Do people seriously experience outage every day? I really don't know... it always has been feeling like a once-per-six-month thing. Do people have extremely complex Actions that I can't fathom?
> Do people have extremely complex Actions that I can't fathom?
Yes. Think CI jobs that test every candidate PR against a matrix of build targets, run fuzzing, run simulation tests, run bench regression tests, etc etc. Modern CI workflow automation has reached way beyond what a pedestrian can fathom if you’re not on the wave.
I remember visiting GitHub's downtown SF HQ sometime around 2014 or so... it was soon after they closed their first significant funding round, and years before they were purchased by MS. I had a friend who worked there as a very early employee. I was at IBM at the time doing AI stuff.
I remember saying to myself, "every single meeting room and common area in this building is designed around the consumption of alcohol--the long bar downstairs, the meeting room modeled after an airport lounge, the meeting room modeled after a smoking club, the meeting room / roof deck...
A year or two later they had that public "me-too" snafu (years before me-too) that led to a founder's resignation, a whole bunch of other people leaving, and then Microsoft acquiring the company. I wondered back then, is this the end of the company?
Perhaps so, but perhaps not... Here we are, 8 years the acquisition, only now lamenting a slow demise. That's a nice run for a startup acquired by a behemoth enterprise software company. With the exception of Redhat (which is debatable,) IBM had no ability to keep a software acquisition's culture, verve, or ability alive past a year or two.
it was kind of a miracle that it held together as well as it did pre-Microsoft. I think to some degree, they got lucky, and were able to coast on being in the right place at the right time. And then because they were so central they attracted some amazing talent who managed to keep the thing scaling up _despite_ the culture.
If Github were shut down, it would feel even worse than if Hacker News was shot down. I am github user 1520. Signed up a just few days after Mithcel on february 2008. I remember the early days sitting in a hotel lobby next to Chris Wanstrath and discussing a bug I found on github. Not ready to do the switch yet.
It is sad to see how far GitHub has fallen. Will also be interesting to where mitchellh takes the project, I imagine codeberg and sources are possibilities.
I feel this. :/ It also just reminds me of everything we've lost in tech since the 2010s. When I used to put Octocat and Google stickers on my laptop and go to conferences every year and everyone was so optimistic and vibrant.
The big idea is all agentic interactions should critically rely on GitHub APIs. Code review should be agentic but the labs should be building that into GH (not bolted in through GHA like today, real first class platform primitives). GH should absolutely launch an agent chat primitive, agent mailboxes are obviously good. Etc. GH should be a platform and not an agent itself.
Why do I want that running on somebody else's computer? It's bad enough that most developers already rely on Anthropic or OpenAI. What value does a remote working repo add?
People suggesting git bug and other solutions miss one important part that also makes GitHub sticky: They have an app, being able to look at issues on your phone, getting notifications and being able to review things there is worth a lot.
User 2882 here. What I know is that once a mass exodus occurs from service A to service B, the issues of service A that led people to leave it for service B will start to appear in service B as well.
Really feel this. Along with group chat (irc), GitHub is the best form of social networking I’ve ever experienced. It’s how my co-founder and I first connected some 6-7 years ago. It’s the real LinkedIn for devs, where the posting activity is the work itself, rather than posting about the work. A truly magical place, while it lasted.
On a much smaller scale (niche personal projects), I'm also planning to leave Github (probably for a local forgejo or even gitweb).
The vast majority of features GH offers are of no use to me. In fact, in the age of vibe coding, zero-friction drive-by contributions are a net negative. The UX has been steadily dropping for years. The recent abysmal record in availability and bugs is just the last drop in the bucket.
The writing was on the wall the day they were acquired. They had a good run, but those days are long over.
Everyone should have abandoned ship sooner, namely when they were consuming content for Copilot without permission. When it became obvious that pushing your code to GitHub meant giving it directly to Microsoft I stopped using it altogether and ran my own git/gitlab/gitea (I've changed approaches several times).
> past month I’ve kept a journal where I put an “X” next to every date where a GitHub outage has negatively impacted my ability to work2. Almost every day has an X
Is it really this bad?
I've seen people complain about Github, but I thought it was more of a theoretical inconvenience rather than a real practical one. As in, the uptime for a serious software company should be 99.9, but two hours down just today, and constant outages over the month that they noticed... that seems way worse.
Yeah, we use GH heavily at work (not so much GHA for critical workflows, thank god). They have an outage that breaks our git operations once a week at least. Like, webhooks not delivered, PRs not showing up, git operations not working, API issues… and that’s not counting GitHub actions which we only use for noncritical workflows
The downfall of GitHub is sad, having a centralized way to find cool open source software is amazing. I use the feed of what people I'm following are starring, tags and code search to find amazing and interesting projects, and I'm afraid I'll be missing out on great but hidden software since there is fragmentation when people leave GitHub.
And the search capabilities of alternative Forges are not the same (Mostly due to costs I assume)
You're not alone. At my company, we're now making plans to self-host our Git and CICD. I probably can't sell them on Gitea+Drone or Forgejo or another open-source solution (even though it'd suit us well), but we're still going to find a solution that isn't dependent on someone else's platform not sucking.
Outages aside, I have not put any serious work (of mine) on Github since it came out that they trained CoPilot on everyone's code without any sort of opt-in or details about how licenses were honored. I moved all my code, and I stopped doing the Hacktoberfests as I realized their incentive to have us all do it. All the good will I felt participating in FOSS was lost almost instantly. I still make FOSS and still participate in other's projects where I can, but I host my own stuff elsewhere.
GitHub needs a Sonos moment, after they launched their failed new app that made everyone angry and leave they got a new person in and I've seen them actively respond to issues on BlueSky with honest responses and not corporate fluff ever since while also turning the ship around.
Come to the Gnu Savannah (jk) strange to see so many projects moving off GitHub. I always used gitlab, and only grudgingly had a GitHub, because that is where every project was. So while seeing people move off GitHub validates my choice to not personally invest in it, I can’t help but be a little sad that
We are splitting across the different git providers.
All this because Microsoft won't sunset the crap that is Azure and rebuild something reliable from ground up. GitHub survived on Ruby On Rails - which was notorious for being slow at scale back then - and still managed to have better uptime than all the execs at Microsoft managed to do so far since its acquisition. What a shame.
microsoft destroyed github: they were careful at keeping classic web (noscript/basic (x)html) support for their core features... and after being bought, everything broke steps by steps.
Now, you must have a whatng cartel web engine to interact with most of the basic features.
Thx microsoft, again.
devs should start to leave microsoft github, but for a forge which respects the web (namely which has a web site, and which is not only a web app).
Agreed. Tech-bros think this is a flex. But at some point americans need to recognize when they have a unhealthy relationship with work, and with consumption.
Because this is affecting the planet, our social ties, and everything else. And it's having impact on all of us indirectly
From a security perspective, centralization cuts both ways.
Large platforms like GitHub have strong security teams and fast patching, but they also concentrate risk. A single vulnerability or abuse pattern can affect a huge portion of the ecosystem.
Decentralizing critical infrastructure doesn’t eliminate risk, but it distributes it.
Is there any service left that will just host your git and offer issues and PRs without cramming anything else down your throat, especially automated help, LLM based or not?
Ideally with private repos for free or a modest fee.
Gitea doesn't count because they only want to sell hosting to large organizations. The pre MS github model for private repos was just fine(tm).
>I’ll share more details about where the Ghostty project will be moving to in the coming months. We have a plan but I'm also very much still in discussions with multiple providers (both commercial and FOSS).
what a cliff hanger!
As someone with similar warm feelings for GitHub, it's kind of sad to see the fragmentation but I have similar frustrations with the recent outages. Perhaps it's time to explore the idea of unbundling the social/discovery layer from the code hosting/dev tool so we can live between the myriad git/jj hosts but still do "social coding" together.
Have not had such big outage issues as what's described here, although I have noticed more stability issues lately. Is this worse while Europe is sleeping maybe?
Typically we see it when the US comes online, we’ll see 500s on availability across all of GitHub — either corroborated by number of active users, number of updates GitHub is pushing (being a mainly US company), or a combination of both.
Github is Microsoft. Nothing more needs to be said, and all of Microsofts products and services must be avoided like the plague they are. A lot of young people have not had the "pleasure" of dealing with Microsoft historically, when open source was a cancer, so I understand why they make the same mistakes that people did in the 90s and 00s.
Github has been all right for me because I don't do too much collaboration and I prefer not having to worry about the security implications. But it just struck me that I have my own infrastructure on Tailscale. I could probably just use Github as an alternate remote and use my own infrastructure to store the code. I imagine a gix + axum + maud should be able to give me my own git web host.
The existing open web hosts are just super heavy. 512 MiB minimum RAM and stuff is totally unnecessary though I have hundreds of gigabytes of the stuff. And then you need all these DSL YAMLs around and a job runner etc. I think I could probably fit the whole thing into a much smaller size. And I have kube running already so job management isn't the hardest thing in the world. Nightmare for SOC2 perhaps. I guess we'll see.
I think this is all home-forgeable now. The advantage of Github for OP was the social aspect, clearly, but I don't use it for that. And I'm a really late user 7,322,596 from 2014!
I never had any positive relation to Github. Free software should be developed on free platforms. So I very much welcome this. Fuck Github. Every single outage Microslop vibe codes is a good thing.
But it's very interesting to read about the author's very different perspective. User 1299 in 2008 is wild. His Github account could share the Radler I'm drinking right now with me.
I see that it's genuinely sad, but proprietary software and services make you completely dependent on someone else. If you want to rely on something for the future it has to be FOSS, everything else is a rug that will be pulled under your feet eventually.
> I see that it's genuinely sad, but proprietary software and services make you completely dependent on someone else. If you want to rely on something for the future it has to be FOSS, everything else is a rug that will be pulled under your feet eventually.
I'm with ya, but building services at the scale of Github, (even when it was a fledgling) requires resources and budgets that very few FOSS projects can even try for. So any replacement is essentially guaranteed to happen commercially.
The original git model enabled part of what was necessary for a fully distributed social phenomenon, but it didn't even go half way. None of the critical social aspects of Github were, are or will ever become distributed, now that a gatekeeper monopolist owns it.
If you want a true FOSS replacement, it's going to need to do at least an order of magnitude more prep work before launching. We've already seen what we get when somebody puts up a plain git server, and we've seen when a single company extends it to become social with a proprietary, non-distributed model.
A better future requires much, much more up-front work.
I think GitHub has completely lost the plot over the last year or so, I don't think the stuff I work on will leave any time soon but I'm slowly losing my patience with github.
The other week I spent about an hour trying to figure out why my actions jobs were just stuck on waiting and not starting.
For my personal stuff, I think I'm going to migrate to either my own selfhosted instance of something like gitea or codeberg, the juice just isn't worth the squeeze anymore imo for GitHub, even with stuff like free runners and pages.
I personally think this is mainly attributed to GH Copilot and I would love to know if MS/GH even makes a profit on it.
I really like forgejo, but for OSS it's a complete no-no unless they want to manage PRs by email. Maintaining a forgejo instance and allowing anyone to join is a recipe for headaches. Until forgejo figures out the federation aspect (allow to send PRs from other forgejo instances, or some other distributed way), it will be hard for OSS to adopt them and keep the collaboration aspect.
Yes, I love their daily UX optimisations like showing issues comments in time ascending and having to click read more several times to get to latest comments. Each and every time.
why not just setting up github enterprise? i mean it's still an infra to take care but if you are willing to pay for it, you may as well? from my experience the other git forge doesnt provide the same feature sets and api as github, like gitlab ci is actually pretty limited compared to GHA, there is no concept of github apps for other providers too, but maybe you just want a code hosting..
Im still waiting for... Basically anyone that has used TFS (what microsoft had/pushed before acquiring github) to do a similar post, detailing how they miss the tool original concept. I'm sitting down, don't worry about me.
What are those strengths? I've worked with projects hosted on GitHub, GitLab, and Azure DevOps at my current job, and was generally not impressed with AzDO (mostly looking at CI stuff).
prs not being visible because search is down, various ui elements not loading, pushes failing, merges failing, gha runs that fail with random errors or take forever to schedule
i literally do not recall the last day that passed without someone on my team noticing that some portion of gh was degraded.
I've been impacted once: An action that failed to start (a PR check), then the merge button on that PR having no effect. Thankfully there was no urgency. It's a bit distressing because GitHub is kinda the engineering hub of the companies. We do have copies of the codebase on our computers and can launch build from there, but we have a process for a reason, and bypassing it is hacky.
codeberg, self-hosted forgejo, gitlab, still-beta sourcehut, tangled? github was “the git community” and now it’s fracturing—you need accounts everywhere, you can’t easily discover neat projects
i like tangled if only because it’s built on atproto which emphasizes ownership and transferability of identity: something that would make the move off github so much easier
n=1 but i don't really discover new projects via github, it's mainly here, reddit, or via colleagues. then again, i selfhost forgejo so don't have a real presence on github
This comment doesn't add anything novel to the discussion, but is worth adding I think because hubbers and MSFT folks read HN - I too am evaluating leaving personally. Professionally, we're talking about it loosely, and if it continues it will become an increasing likelihood.
Is "migration to azure" or "microsoft acquisition" a cause or a symptom?
I'm wondering to what extent the natural life cycle of SaaS products comes down to: the company grows, the old guard with good technical taste move on, bad technical decisions are made, quality declines, users move on.
It's odd. I've been having the same feeling as well. Earlier this week, they sent that email about copilot, which I don't use but pay $10 a month for and I canceled my subscription.
GitHub has become a place where you seek people’s attention. There are other places you can freely host your projects. GitLab was always available. I just haven’t logged in for I don’t know how long. An open source project is essentially a show window to the internet by a lonely developer. Ghostty has already established a great community. It’s already on display on a skyscraper. The project is mature enough that it needs a dedicated discussion forum or something like that. I am excited to see where it will find home and how it will evolve.
Possibly in a few years from now we'll get actual data about how many outages we've seen or how much have x services degraded, overlapped with the push for "AI everywhere".
One can only hope that as people get tired of Github and move to other services, we'll see better Mercurial options. I feel like git itself mainly gained in popularity because of Github.
Either way, the thing that irks me about the Github situation is that so many people joined Github specifically because it was "where everything was happening". And now they realize that having one place where everything is happening is not really a great situation if that place starts going south. We need a range of providers with good interop rather than centralization.
Imagine if MS just did a git revert all the way back to ~2020. That was peak GitHub for me. We got some niceties the first couple of years after the acquisition - free private repos, Sponsors, secret scanning, a new mobile app and CLI - but things were still pretty stable, before their architecture and the little UX touches got destroyed.
Anyway, good luck with the migration. Curious where you land. And honestly? Props for actually following through instead of just complaining on Twitter like the rest of us.
Is it really the case that GitHub had fewer issues in its early days? Or have our expectations just increased as GitHub has effectively become a critical piece of infrastructure? Go back to 2010 and half the functionality that people are complaining about (e.g. actions) didn’t even exist.
The author is entitled to his feelings. People can host their projects wherever they like. However, this is also a huge drama about basically nothing. GitHub is actually much more useful now than it was in its heyday (when it had far fewer features to go wrong).
OP takes issue with GitHub's constant outages and alludes to agents (and Copilot bloat) as the primary cause.
Lots of big services are like this. Google Colab's 'Connect to Drive' is down as we speak. I'm up right now because I know my Runpod VM in Kentucky is going to die rather abruptly and I'll need to manually get it up.
Everything has its flaws.
Microsoft lets you host your code, websites and media for free and
there are plenty of enterprise github users. Where I work currently has an internal github and uses external github.com to host public facing OSS work.
about to launch my first open source project in days. reading this with a knot. github used to be a default; now it's a decision. and watching mitchellh agonize publicly is the honest preview every new maintainer gets from now on.
I think this Twitter question and response (from the author) is helpful to understand the problem:
Question:
So, I'm also annoyed wit GitHub's stability (especially lately), but I'm curious: Ghostty has only a handful of PRs per day (excluding robot contribs); how is this a real problem? (and yes, I read your blog article).
Response:
1) The robot contribs don't auto-close if GH is down (cause it relies on GHA). We have retries but its pretty annoying.
(2) A PR isn't one and done. We need to comment, we need to run tests (~80 per run), and we do this multiple times per commit (due to review back and forth). So one PR has a lot of GH reliance right now.
(3) PRs tend to batch up, e.g. we don't do PR review constantly because all of us have other things to do, so we usually will try to review/merge multiple at one time. 3 PRs per day = 20 per week, which is a ton for volunteer time!
(4) We try to coordinate merge parties across maintainers in China+US+EU and if GH is down during our small time slice we just can't do any meaningful merging for 24 hours. We could alter our process here but that's just gaslighting.
(5) We get an order of magnitude more issue and discussion comments, which are affected by all of the above except CI. These are particularly affected by GHA/API outages.
(6) Dev work by maintainers happens in non-PR branches that run CI, and if CI is down we can't test our code (since Ghostty relies on a lot of testing we can't run locally, e.g. for platforms we don't have). It effectively pauses work on that branch.
(7) I've had multiple days in that 30-day window where Git operations themselves failed for different reasons. So I couldn't push a branch or whatever.
It just all adds up to be WAY too work impacting. The Ghostty maintainer channel is a stream of "oh GH is down again."
Read the piece waiting for a diatribe on MS's unethical practices, left with an uptime complaint. Ok, if that is what it takes for people to move away from them, we'll take it.
> Lately, I've been very publicly critical of GitHub.
Well, he is not alone with that. Something isn't working - and Microsoft either does not realise it, or does not care. I think the microslop strategy consumed Microsoft internally; it seems unable to change trajectory now. It's like you are driving to a cliff, in a car but you are not the main driver. It's quite interesting to see though - people can now expect "which disaster will hit Github tomorrow".
On the other hand, I also think it is time that Github gets some serious competition. Gitlab is not that competition; codeberg also not really (they'd need to up the useful features by a LOT and keep on driving that - I just don't see they have enough energy and momentum for that, but as a smaller source code hosting platform they are not bad either).
If I was OpenAI / Anthropic, I would see this as a massive opportunity.
I mean, why wouldn't you want to consolidate git repos, a heroku/fly.io/vercel like container system and direct access to web-based coding tools. They have the coding models and agents, slap a web interface over Claude Code running in a container, allow for commits and deploys. Control the entire stack.
> To the "Git is distributed!" crowd: the issue isn't Git, it's the infrastructure we rely on around it: issues, PRs, Actions, etc.
Yet again, I wish the prevailing SCMS were more like Fossil, where issues and forum posts, at least, are part of the repository (and everything lives in a single sqlite file). (Of course Fossil actively opposes "pull requests", separate issue)
> (Of course Fossil actively opposes "pull requests", separate issue)
Not opposition, but very little incentive for the primary developers to implement the feature. Fossil's own developers happen to be the same as SQLite's developers, which doesn't accept outside contribution as a policy. It results in Fossil's features being predominantly, but not exclusively, the same features needed for SQLite and little else.
what exactly is going wrong with github aside from all the outages in the past x months? i honestly don't find it particularly disruptive to work/personal stuff. excuse my ignorant, maybe i don't use github enough to know what causes this fury...
fwiw - i do keep a fair amount of code in my computer. i don't push everything..
<rant>
I feel like this is the classic tale of corporate greed. Startups should stay startups.
From the users perspective, I always hated the fact that you are the product.
They create a great software, give you nice things, you fall in love and start to use the software, even advertise it in your circles because it's soo good. Then they sell the whole thing with you and your bros for big buck, and the new management slowly start to squeeze all the money out of it to justify the purchase while ruining the product.
</rant>
It really has been infuriating lately. Between this and my company's proxy screwing with HTTP/2 at least once a day the frustration is very very real. While I'm nowhere as invested in GitHub its decline does make me sad.
Hear me out: Github needs ads . If option A is downtime (and data integrity issues), Ads are more favorable. The terminal UI and PRs are both captive real estate that developers have to pay attention to.
There is a simple cost equation of 40-100x demand vs a fixed op-ex budget for the org. Github can either 40x their paying customer fees or try to monetize all of the free vibecoder (and open source) traffic.
Ironically, I was thinking that the Github downtime is an American view in and of itself. For us living in the European time zones, Github is hardly down during our business hours. It's mostly down during US business hours, then demand is highest.
I'm not sure how we ever could have expected GitHub to continue with or add quality when being built by the same company that also builds MS Teams. There are clearly the wrong quality levers at work inside Microsoft.
Yes, it seemed like Microsoft had a brief interregnum period of about 10 years where they seemed to have a renaissance and a genuine culture change and a concern for quality and initiative seemed to take hold.
And for many of us who came into the industry in the 90s this was a strange period because actually post-Gates/Balmer MS suddenly seem not so bad?
But that was until the first deals with OpenAI and the first round of layoffs. After Musk's purges at Twitter, MS was the first to really join in the fray.
Since then the old MS is back. Clearly as Machiavellian as in the past. But kind of sadder and more pathetic.
But honestly I'm also a bit confused by the framing some people have this thread because I remember GitHub always having reliability issues in its early days. It and Twitter were both famous RoR projects with notorious and constant outage issues in the 2008/2009 time-frame.
Ah yes, after a decade of being one of the worst pieces of software with 10M+ MAU, literally only gaining market share because of monopolistic bundling practices.
So bad that if a startup had made Microsoft Teams they would've gone out of business after a year.
As an aside, I always wondered why GitHub had a web interface. Admittedly I’m a pre-web SCCS/RCS “old timer” but I wouldn't have put a web interface on it at all.
I know this is ridiculously dramatic, but its the truth: I actually cried writing this blog post (tears hit my keyboard, I'm embarrassed to say).
Nobody should cry over a SaaS, of all things. But GitHub has meant so much more to me than that (all laid out in the post). I have an unhealthy relationship with it. Its given me so much and I'm so thankful for it. But, it's not what it used to be. I don't know.
We've been discussing it off and on for months, really started seriously discussing it a couple weeks ago, and made the final decision a few days ago. Putting metaphorical pen to paper and hitting "publish" makes it so very real.
I'm sure folks will make fun of me for this. It is a stupid thing. But I truly love GitHub, and I hope they find their way.
Hi there! Longtime fan and hubber here.
It's okay to have emotions. I have similar emotions. I'm GitHub User 22723 which is effectively the same as you (considering there's ~180m GH accounts nowadays)
My version of your post reads differently:
"GitHub only gets better if people who give a shit stick around to make it better"
Walking away would be easy. I felt that way when I left Heroku ~six years ago. I left that job and never opened the Heroku dashboard again, after nearly a decade of happy use. I felt that it was irredeemable, and though it took a while, Salesforce did eventually succeed in running it fully into the ground.
I don't feel the same about GitHub. It is precisely because it's precious that I can't walk away. I'm not the only one here who feels that way.
In the past few years, GitHub has absorbed both a fundamental paradigm shift (agentic coding) AND several different hockey sticks of growth. It's messy. I'm not always proud of the results or the product choices we are forced into. But none of it feels like the Heroku/Salesforce debacle. Occam's razor applies here: it's not "more AI coding" and it's not "big bad Microsoft." It's scale, and a fundamental shift of the ground under all of our feet.
I hope we do the things that will make you want to come back. I hope we spark that joy in you again! It's not stupid to have big feelings about something that is so central to our lives as developers. Fuck that noise.
> "GitHub only gets better if people who give a shit stick around to make it better"
This is true but misleading. Unfortunately.
It is a true statement for developers working in GitHub at Microsoft. It's not a true statement for users.
There is no avenue by which you make GitHub better by continuing to use it as it has been.
50 replies →
> "GitHub only gets better if people who give a shit stick around to make it better"
It is a megacorp that is mainly in this situation because of its relentless pursuit of exponential growth for the benefit of a very select few to the detriment of everyone else (including GitHub employees such as yourself). The hockey sticks are there, but how they've reacted to them - which is what has lead to this situation - is entirely because of the above. If not for that, it could've reacted to them differently.
It does not deserve to get better.
It would be very good for society if GitHub's market share massively declined, if everyone moved away. It wouldn't be good for you personally, but it would be good for everyone else. There is nothing positive about a single company having access to everyone's code.
Just look at all the tricks you've been playing, automatically opting everyone in to having their code used for LLM training. [0]
GitHub shouldn't get better. It should decline in popularity.
You know full well that it is undeniable that your competitors gaining market share would be good for everyone as a whole, but comp juicy and emotional attachment to people there and the pre-acquisition times where it used to be a great company (those times are not coming back) and your past with them etc.
[0] https://www.theregister.com/2026/03/26/github_ai_training_po...
This is called brand loyalty, and it's one of the first thing they'll abuse.
I used to think people who said Github had become very unreliable were exagerating, but I can't miss it now. If you want to keep people, you have to actually go down less.
It's interesting that internally you had a very different experience with Salesforce buying Heroku and Microsoft buying Github. From the outside it appears to be analagous (except github is degrading quicker than Heroku did?)
11 replies →
If anyone reading this is curious of their own, you can go to https://api.github.com/users/YOUR_USERNAME_HERE and fetch it.
My ID is just over 10,000. Crazy to think of the journey that I've had in computing since I signed up for GitHub.
56 replies →
Just an observation: The different approaches mentioned in the replies to this post seem to all neatly fall into one of the three types of individual response (exit, voice, loyalty) there are to any sort of decline in/of firms and organizations of any kind within Albert O. Hirschman's well-known economic framework, originally laid out in Exit, Voice, and Loyalty: Responses to Decline in Firms, Organizations, and States (1970).
Personally, I find "loyalty" perhaps the most fascinating one of those, being "irrational" for the individual almost by definition but sometimes, for example, proving out to be the only "glue" holding an organization together through a period of incurable-looking decline followed by an eventual recovery (in the lucky cases).
> "GitHub only gets better if people who give a shit stick around to make it better"
At a basic level I appreciate this sentiment. However, the common dysfunction I see in large corporation is its not the lack of people who give a shit. Its lacking a sufficient number of people in positions of power that give a shit -- such that they can actually make change happen.
All too often competing pressures (features, profit, delivery speed, politics) take precedence; not leaving time for things that would really move the needle. In essence, too many leaders are happy to ship garbage; they don't care (or don't know).
If Github were to put out a statement saying "service quality is our priority", it is fairly meaningless. If they added "here's how we'll get there", maybe it helps some. Moreso -- "from now on executive compensation is tied to these SLOs", then maybe something would actually happen.
2 replies →
> "GitHub only gets better if people who give a shit stick around to make it better"
What's the mechanism of action here? What changes if I stay? What changes if I give more or less of a shit? Is there javascript telemetry feeding my shit into a dashboard with a calibrated shitometer for executives to consult when they set quarterly objectives? My account is six weeks younger than mitchellh's and I've been watching GitHub fall apart for the last year, what will happen because I stick around to watch for another year? Besides that I will get covered in shit.
You're an employee. What changes if you stick around? Back in October 2025, the GitHub CTO Federov prioritized moving to Azure above feature work (https://thenewstack.io/github-will-prioritize-migrating-to-a...). Yesterday he recommitted to it (https://github.blog/news-insights/company-news/an-update-on-...), writing "We started executing our plan to increase GitHub’s capacity by 10X in October 2025 with a goal of substantially improving reliability and failover." GitHub has had six bad months of increasing bugs and sharply decreased uptime, and the CTO just recommitted to staying the course. You've explicitly been directed to move to Azure, not to give a shit or to make things better.
So I'll defer to your direct expertise. From the outside, Heroku stalled and died because Salesforce prioritized everything else in its business above Heroku. Are GitHub's priorities so different? Does you giving a shit make Azure and Copilot the best top priorities for GitHub? Will Azure and Copilot be why I stop seeing SPA jank? Will Azure and Copilot be why I can see my list of open PRs? Will Azure and Copilot be why I see something more than the 500 unicorn? Will Azure and Copilot stop the spam PRs that want to undermine the quality of my code? Will Azure and Copilot lead to anything other than the same corporate dismissal and dysfunction that led to Heroku? Will you giving a shit matter?
> In the past few years, GitHub has absorbed both a fundamental paradigm shift (agentic coding) AND several different hockey sticks of growth. It's messy. I'm not always proud of the results or the product choices we are forced into.
Excellent example of why centralization is a bad thing. A Git “hub” is not a thing that should have ever existed for a self-described “distributed” version control system.
3 replies →
> t's not "more AI coding" and it's not "big bad Microsoft." It's scale
Besides "That's what makes us money and pays my bills", there is no real reason to keep building github as this centralized, all-encompassing system that needs to work at global scale.
Engineering is about understanding that everything is about trade-offs, and eerything keeps pointing out to the fact that wrong choices are being made there. You can throw as many people as you want or all the MS money at it, but as long as Github "engineers" that keeps overindexing on Efficiency at the cost of Resiliency, it will feel like this pile of unusable crap
looks like you work at github.
I completely understand a "people who give a shit stick around" mentality if you work there, but you can't expect users who run a business on it to stick around if it's broken.
2 replies →
Github is Microsoft, who even cares? How can ppl be so caught up in a brand name? Microsoft doesn't care about you, why do you care about Microsoft? Things always change, just move on when the time is right.
2 replies →
I found out today that I am user 6082. I have been using github since the rubyconf (railsconf? I can't remember) where it was announced. I loved octocat. I was a git fanatic. It has been extremely disappointing.
I am using fossil now. I kind of love it, just a sqlite file with a very trim binary to interact with it. I get all of my things that I want (wiki, forum, issues, docs, etc) all in one file.
But that's just for fun. At work we are still tied to Microsoft Github. Just typing that out feels dirty.
"Stick around to make it better", exclaimed the abusive partner.
github hasn't absorbed agentic coding, though. agentic coding has absorbed it, and as a result it's quality is suffering.
the thing about github that is so maddening is linus gave us the secret with git itself. then we reinvented centralized source control using git and called it github, and here we are.
2 replies →
As someone with the ID 1653, I've totally given up on the thing. I've even created my own rust based forge, ironically, hosted on github at the moment.
The avalanche has already begun. It is too late for the pebbles to vote.
Yeah, be careful not to gaslight yourself into trying to "tough it out" with bad vendor relationships. Sometimes you do need to know when things aren't good/healthy and it is time to walk away, as sticking around just ends up being needlessly flagellent.
Especially with corporate owned software or SaaS ecosystems!
Sounds like you made the right choice with Heroku back in the day. I feel like this is Github's Heroku moment.
Considering the size and scale of Github, do you feel like it's become closer to an infrastructural public good rather than a privately owned product?
The amount of impact I've seen to businesses around the US at least might as well be akin to a Covid shutdown, and that certainly has me thinking about what the overall impacts are on the US economy overall.
3 replies →
I appreciate that you're staying inside with that mentality.
Like Mitchell, GitHub was once a dream job for me, and it just never lined up pre-acquisition. I shared many of Mitchell's habits too, about GitHub being my reading material. Until some time after passing 2000 starred repos, I had literally read every line of code in each of them. GitHub still feels like home to me, as a user.
Good luck, and we're all counting on you.
(359439, which is quite high for this thread, it seems!)
As Albert Hirschman observed in reflecting on his seminal "Exit, Loyalty and Voice": "an organization needs minimal, or floor, levels of exit and voice in order to receive the necessary feedback about its performance".
Don't feel too bad, you are both essential to the process that ends in Github improving (or imploding).
The heroku mention here struck a chord for me. I don’t feel as attached to GitHub for some reason but Heroku was the first web host I used where I felt like “this is how cool a web-based tech-oriented product can be”.
So crazy to see how money can ruin such a good thing.
Github isn't a public good or a person; it's a product for a for-profit company, whose aim is to squeeze profit out of you. They care nothing for you and will dump you the moment it's profitable.
I would invest your energy in something worthwhile like an open source project, a non-profit, a social or political cause, a family memeber, etc.
> Occam's razor applies here
I think the simpler explanation is clearly that it's a for-profit company and these problems aren't worth fixing, and not a speculative engineering excuse. If Microsoft wanted to invest more, including in uptime, they could make it happen. They have over a trillion dollars.
1 reply →
huh, I've never thought to check my github id. I don't remember myself being an early adopter.
What you built was a community, not a website owned by Microsoft — it could port just fine to GitLab.
“I won’t leave, I’ll fight to make this place better!” is a laudable trope ofc, but in this case you’re not making any place better, you’re just defending shareholder value. IMHO :)
Fyi your HN description still says Heroku
1 reply →
"GitHub only gets better if people who give a shit stick around to make it better"
This only works in democratic settings. In capitalist corporations, typical liberalist parliamentarism and so on it does not work, only coercion does, which might be peaceful, like a strike or boycott, or it might not be.
Holy crap, just found out I am 1371. Wow.
7 replies →
fuck microsoft. it absolutely is the big badness of that monster. microsoft's sick monopoly has dragged humanity back by years from where we should be. every hour wasted, every email lost, every skilled career sacrificed to their garbage is the future lost.
You sound like you just want to make the world a better place /s
2 replies →
Hi, tangential but your post mentions only two pronouns when the recent trend is to mention 3 out of respect for gender fluid people who often use slight deviations in the third pronoun as an indication of their fluidity. Hope you do better
2 replies →
I can feel the frustation, nothing dramatic about expressing it
This quote from the post resonated with me:
> I want to get work done and it doesn't want me to get work done. I want to ship software and it doesn't want me to ship software.
The sentiment is shared, and github is not the only service making me feel like that, it feels like everything on the web is more flimsy and low quality nowadays. Constant outages, bugs, UI papercuts, incomplete features, what in the world is going on?
Microsoft, Greed, Outsourcing to low-cost-countries who couldn't care less and rotate entire dev teams on you every few months or so, etc...
No AI needed at all. Only humans.
12 replies →
> it feels like everything on the web is more flimsy and low quality nowadays.
Not just the web either. It feels like the whole world is in a race to throw shit together and cash out as quickly as possible: influencers, hustle culture, enshittification, etc.
My pet theory is that all of the global chaos around the climate, politics, pandemic, etc. is leading people to no longer believe in the future. Once you lose that, all that's left to care about is the right now. No one takes the time to scrimshaw the deckrails on a ship they believe is sinking.
3 replies →
> I can feel the frustation, nothing dramatic about expressing it
I think the "ridiculously dramatic" part is the whole love letter to GitHub, not the frustration.
And I think it is fair to say that it is ridiculously dramatic. Which is okay, of course, I'm not criticising here. Just like it would feel ridiculously dramatic (at least to me) if someone explained that they cried today when they stopped their subscription to Netflix in order to move to another service, because they love Netflix so much.
2 replies →
Way overcomplicating design is one challenge that keeps getting worse.
Another gigantic unspoken issue is that people have started building tons of stuff with React on purpose for some reason.
4 replies →
Enshittification has become the winning strategy for companies. If you don’t enshittify you will lose.
14 replies →
It's move fast and break things.
2 replies →
>what in the world is going on?
AI slop code
15 replies →
>The sentiment is shared, and github is not the only service making me feel like that, it feels like everything on the web is more flimsy and low quality nowadays. Constant outages, bugs, UI papercuts, incomplete features, what in the world is going on?
Have you ever tried to run anything from the 80/90s era? Segfault everywhere, "fatal error was successful", kernel panic, BSOD, screen freeze for any reason and its opposite.
Nothing serves better good all time than bad memory as they say.
Not that the gigabit of useless crap to show essentially a few ko of text is fine, but the abuses and horrors that humans commit just shifted a bit where they land, it's not like there was a time were we had a land free of human dirty stuffs.
2 replies →
(Needless) complexity is going on.
KISS and you sleep better.
That and the problem of forever chasing trends and never saying: "It's done" without reinventing everything every couple of years (trends again)
Sounds too easy? It is of course simplified, but the core still holds true.
GitHub just worked, but they had to migrate to React because "that's what everyone else uses"... Pure Enshittification.
6 replies →
> I'm sure folks will make fun of me for this
To be honest, the blog post is quite a lot of self-indulgent waffle. But I forgive you for that, "each to their own", as they say.
What I won't forgive you for is writing such a long blog post and then completely missing the bottom-line.
Do not write "I'll share more details about where the Ghostty project will be moving to in the coming months".
If you're going to make me read such a long blog post, then at least have an answer ready-to-go for the critical question that everybody is going to ask !
Better yet don't write the post at all until you actually do something.
"I'm going to become a vegetarian" vibes.
Spool of Wire Guy or Wiregate refers to a viral video of a man (named Dan) telling his wife (Cindy) that a spool of wire he's had for 40 years is almost at its end
The spool of wire became a prominent metaphor on the app, representing something that might seem meaningless to others, but holds sentimental and nostalgic value to its owner.
https://knowyourmeme.com/memes/spool-of-wire-guy
I do recall this meme and I empathize with him and also Mitchell above. It's annoying for people to not understand your feelings or make fun of them especially if they're reflections on years past.
Anyone who makes fun of you for feeling things probably isn't anyone you want to listen to, anyway.
Thanks for being human and making ergonomic software for humans.
> I know this is ridiculously dramatic, but its the truth: I actually cried writing this blog post (tears hit my keyboard, I'm embarrassed to say).
No, it's not. There are things we like/love in our life, and we rightfully get sad when things go bad in the camps we like, support.
> I'm sure folks will make fun of me for this. It is a stupid thing. But I truly love GitHub, and I hope they find their way.
I personally won't and will be angry to the people who do. Been there, done that for different things. We're human, this is normal.
For finding their way, I can't be that optimistic, unfortunately. Sorry about that.
I thought you like worked there but with the additional context that you never did, yeah cringe
There isn't inherently wrong with loving a tool or been sad when it it becomes something you can't love anymore, we are tool using monkeys after all - it is perhaps our defining characteristic.
I'd be absolute crushed if Linux (for example) morphed into something I could not/no longer wanted to use, part of the reason I use open source wherever I can is because that is less likely to happen, Inkscape is still inkscape nearly 20 years after I started using it, so is Gimp, so is KDE, they've all changed but the essence of them is still the same (so has Linux).
KDE's hard-switch to Wayland broke so many things in my workflows, from what used to be a perfect system. For keyboard expansions espansso/ydotools crash bi-hourly and I couldn't pinpoint the source, clipboard sharing between applications doesn't work anymore, global shortcuts have been limited... The essence is the same, but it is so broken that it has a real productivity impact that will require a lot of effort to correct, and would depend on upstream fixes...
Gnome. If you liked Gnome 2, by now you're crushed. At least you can use Mate Desktop.
1 reply →
Nothing stupid about caring deeply about tools that shaped your career. GitHub wasn't just a SaaS for a lot of us it was where we learned to build. The fact that you're emotional about it says more about how much you gave to that platform than anything else.
Ghostty will be fine wherever it lives because people follow the project and not where it's hosted. Best of luck!
So true! This quote from the blog post really hit me:
> Since then, I've opened GitHub every single day. Every day, multiple times per day, for over 18 years. Over half my life. A handful of exceptions in there (I'd love to see the data), but I can't imagine more than a week per year
How could you not feel this way about a tool you willingly use this much? Perhaps if your employer is forcing you to use it, its different. But maintaining OSS? that's a labor of love. How could you not get emotional?
> tears hit my keyboard
That is indeed a dangerous slip. I hope yours wasn't an Apple machine. Warranty might be an issue, because even if just one key got soiled, they will propose you should replace "practically" the entire machine (or rather make you; because well, replacing just that exact part that was damaged would be less expensive and hence less efficient and environmentally unfriendly).
On the other hand, not at all ridiculous; dramatic yes. I almost felt sad when Orkut shut down. Almost. And around the time XMPP/Jabber stopped being like email when Google/Fb pulled the plug. Can't remember whether it was at the same time. I became numb to such fast and slow metamorphoses a long time ago and I feel sad about this numbness. It's a forced cynicism I'd say. These are such inane corporate events/changes and yet these are so deeply embedded in our lives. Without check and any power over them. So perpetual cynicism works.
PS. I really found Ghostty to be cool (and fast!). Sadly, I reverted to stock Terminal, not because Terminal is as good, but because I no longer have/had much terminal usage (until I get back to work/coding again, and I hear things are happening in the terminal a lot more again with our world's new coding toys, LLMs, and whatnot). I also heard you on a podcast recently, and it was very interesting, and since then, I want to try Ghostty again, without even a real need for it yet.
I feel you mate. When people were scrolling Facebook, I was scrolling github, being so excited to see so many people building things together. Commits popping up in my stream were making me feel we were improving the world, bit by bit. It was an happy stream, compared to the depressing stream of Facebook. And then Microsoft bought github. And I knew it would only be a matter of time before it would fell down. It also made little sense to build all our beloved open source projects in the living room of the entity who was so harmful to our community for years. So I left github and joined several gitlabs. But I never found back this central steam of "look at open source being made in real time". We need a decentralized gitlab with ActivityPub.
I don’t know if you remember but we met at cfgmgmtcamp in 2016.
https://imgur.com/a/auPVRuq
We weren’t even in the same circles and this was my first good conference, but my own little company that I worked at was full of motivated hackers that were trying to wrap our heads around what you already understood.
You took my comments about on-boarding and documentation very humbly and you knew what I was really saying was: keep it up.
You sure did keep it up.
Those same team mates are here with me using TF at a different company years later, and we’re still pushing left.
Those colleagues just said “it’s art and science”
… and when the art gets ripped away from you, what you described is a natural reaction.
Still, keep it up.
> Nobody should cry over a SaaS, of all things.
We don't cry over things, we cry over what things mean.
I don't see anything wrong with grieving the loss of a community and environment that led to so many meaningful experiences for you.
> I truly love GitHub, and I hope they find their way.
I jumped ship as soon as they added MFA. I vibe-coded my own raw Git repository reader to help consolidate my other repos (BitBucket, GitLab), which inevitably started to impose more restrictions (disk space, MFA), as well. It's no GitHub, but works, doesn't cache, and is pure PHP.
https://repo.autonoma.ca/repo/treetrek
I hope this doesn’t come across as making fun, but it had never occurred to me that GitHub could be anything more than a tool for hosting my source code. So if you had written this same piece about all the good times you’d had in Windows Explorer, I’d be no less confused.
Can I ask what was there that made you visit the site for anything other than reviewing pull requests and issues?
It's probably not GitHub as such, but the associated memories and experiences. You never miss a place, you miss the feeling of happines you had when you were there, or the people you spent time with there.
People get emotional over a car, over a house, over a pet... you could argue for everything it's just a car/house/pet... you can get a new one.
1 reply →
> Nobody should cry over a SaaS
This is more than a SaaS, for you and the others. Stating kind of the obvious: without it Vagrant, Terraform and heck, even Hashicorp would have not been the same - or probably even existed. Despite probably being a later user of GitHub I share the same feelings. It's so sad to see GitHub, a product and company I once respected a lot, getting trashed by Microsoft and all of these outages.
I wasn’t that invested in StackOverflow but still I was quite invested there.
I do feel kind of sadness right now it is a zombie that current owners are just pumping out whatever is left out of it.
I don’t care about GH I felt centralized repositories like that is wrong.
Q/A was supposed to be centralized because we need people to find the questions and answers in a single place.
GH or others should be just referring to repositories not keep them… be a search engine for decentralized repositories.
Your emotions are totally valid, and I can empathize. You fell in love with a community that slowly got eroded away and no longer exists.
We all understand that. We had some piece of software we still cling on to it (in my case is a copy of paint shop pro 5, corel draw 7 and Delphi 7), despite being completely obsoleted or assassinated by "big industry". I could add CoolEdit 2000 to it, but havent really opened it in a decade.
To be honest, I never understood the fascination with github. Its a hub, of git repos. Not to piss on your parade, because your complaints are valid, but maybe isnt github that as gone sour as much as you have grown out of it. This was your passion, now its over and you move on.
I don't think it is dramatic. I felt a similar sadness around this subject. It's the meaning behind it: the hacker spirit, the naive curiosity, the juveline freedom, being destroyed by the corporate machine. It is a small metaphor that hits all of us in different spots.
And boy, does it hurt.
Completely understand the work/life/hobby fusion.
And I think that you and GitHub went through the stages of life together. They probably weren't exactly parallel, but I bet you measure and remember your life through GitHub's life to some degree, along with the projects you had there.
There's no question that with your drive and acumen that you could build the GitHub that you both had and want. It might be your next chapter.
I felt pangs of emotion reading the post so it’s definitely not just you.
I think because GitHub has been such an important part of my life dating back to the very start of my career - just like you.
And it’s not just the technology, it’s the people. All the great projects there. The countless README’s I’ve dissected trying to setup something new. There’s people behind all of that and that always felt exceptionally meaningful to me.
It has been profoundly emotional to watch GitHub degrade over the past year. It’s almost like watching someone you love slip away. Which I have also done. It’s not the same, but there is something familiar in the pain.
Meanwhile streamers dunk on it in YouTube videos and on X and none of it is funny to me. It’s just tragic.
Now I’m choked up. Dammit all to hell.
I'm sure others have probably said this, but I'll say it anyways. Give Gitea a try. This is what I do. I self-host all my projects and mirror them to Github if they are public projects. And I have distributed Gitea runners across my various servers and they just work and my pipelines never fail me. I'd also highly recommend GitLab CE for similar reasons. But, if you really don't want to self-host, GitLab proper is also awesome and way better than GitHub IMO.
I'm a bit lost about the problem. Is it really about crying about outages? I'm aware of enshittification issues in the broader tech field but the post and this comment don't really say what the problem is. If this is supposed to be some kind of signal and wakeup call, more info would help. For context I'm a lightweight Github user for over a decade, mostly putting up personal projects without much collab, and opening issues in other repos when I find bugs, just cloning and forking stuff (mainly in the machine learning community, but also in general Linux tools). For me it works okay enough, compared with the overall landscape of SaaS. I'm not a fan, don't feel any loyalty and my expectations for user abuse from big tech are admittedly pretty abysmal by now. I'm just not seeing what specifically happened with github to trigger this.
I find the decline of these things upsetting too. I don't know if it slots into enshittification specifically, but there's a phenomenon of decline in general that's so antithetical to where my career began and what I thought was possible. I want to believe we can do better, and ideals can still matter in software.
And I mean, they clearly can; your own contributions are proof of that. We can all do better and the decline isn't a prescription we all need to follow. Regardless, it's tough to watch. Github used to be such an exciting and promising platform.
Wow, thanks for your honesty here. I'm commenting primarily to commend your decision-making which I couch in empathetic understanding. I saw your post and immediately thought, "good, surprised it took {any organization leaving github} this long." I don't hate big M nor the 'github ecosystem' (except maybe github actions, which seems to get 10x the attention it deserves); the challenge is I perceive far better solutions to be chosen which would serve the open source world if we simply deploy a slight increase in cognitive energy.
Whoever makes fun of you over it is exactly the people you want to avoid.
Leaving any emotions aside, all the arguments you gave are technical and carry weight: we are not always in the mood for OSS work -- or even have the time and energy, which happens to be the much more oft limitation -- and when we are, we want our infra to just work. If it does not, that might kill your motivation for a week. Or a month.
For an OSS contributor, the main one even, this is actually bad news. You are doing both yourself and your community a big service by making this difficult decision.
Not everyone can do it. Respect.
I think people today think that compartmentalization is easy but sometimes in life your work and personal life and everything else gets all mixed up and you get situations where others might call it unhealthy but for you, it’s fine ante it’s how you want to live your life.
That’s just to say that crying over GitHub is fine, you’re a human, we cry over all sorts of stuff. Emotions are weird and you should not feel badly for having them.
It's a fair writeup and your thoughts are valid. Businesses have to continue to re-earn customer trust each year - especially when it's mission critical and they expect recurring revenue. I hope they find their way too.
If you're still considering vendors, I think you'll find some of the keep it simple ethos can still be found among OSS friendly vendors -- Codeberg, etc. Good quality & uptime doesn't have to be expensive - just grounded by people that care enough to reject the scope creep and focus on doing one thing well.
"Lately, I've been very publicly critical of GitHub. I've been mean about it. I've been angry about it. I've hurt people's feelings. I've been lashing out. Because GitHub is failing me, every single day, and it is personal. It is irrationally personal. I love GitHub more than a person should love a thing, and I'm mad at it. I'm sorry about the hurt feelings to the people working on it."
Same :( their 9 5's is embarassing
It's good to care about these choices. There are also lots of ethical reasons to leave GitHub, and this makes it easier for people to choose to leave on those grounds, too. Every time people talk about their decisions and normalize anything that's not just having a monoculture where there are no competitive markets and monopolists control entire ecosystems, that's a good thing.
Dramatic or not, it needed to be said and I appreciate you saying it. Nobody would listen if I said it. ;-)
Do you think this is endemic to large software organizations today, or are our needs (and the corresponding complexity) just outstripping the ability of old business models to address it?
People who reach outlier-level success in a field tend to have strong opinions and an emotional connection to said field. It’s probably a non-trivial part of why they are so successful.
No man, I'm with you. I remember when GitHub was a joy to use. Finding new niche tools and projects written by people who actually cared about their work. Needed some simple postgres backup script? Browser GitHub and plenty of people put time and effort in creating something that actually worked.
I was talking about the same thing just yesterday. GitHub with its friendly mascot is no longer. It's now just another SaaS platform that everyone including my non technical colleagues are using. Their push towards everything-AI is the exact opposite of what they stood for in the begining. A community of like minded people who wanted to build great tools and loved software. But yet no longer. GitHub now feels like a soulless SaaS that's trying to hook my onto an enterprise subscription and bring my whole team along so we can all do some agentic coding or whatever.
Was it the platform or the people? The people would be out there doing things without GitHub and they will be there doing things without GitHub.
we can be ai-powered, we can be engineers.
but most of all we’re humans :)
happy to see that some humans can still feel emotions, real emotions, and not be ashamed by them.
> I have an unhealthy relationship with it.
You really, really do. Please, for your own benefit, take a step back and touch grass, literally. There is so much more to this world than Github of all things.
> Every day, multiple times per day, for over 18 years... During my honeymoon while my wife is still asleep? Yeah, GitHub
This is addiction
You feel how you feel and that's totally fine.
What OSS friendly platform will you be moving to?
God would cry too if they saw the world they created. Let the salty tears flow
So far everything is going according to the plan. Humans are really close to make the AI that will replace them and enter into the next phase of the plan.
Or do you have a better idea of what the plan exactly is?
5 replies →
Forgive me if you’re not in a solutioning phase right now … but how motivated are you to fix this?
I’m a big fan of ghostty and also unenamoured with the current state of GitHub and Microsoft.
That is to say I believe this is an opportunity to disrupt the incumbent player and I’m game. HMU if you feel similar and want to discuss.
GitHub died when MS bought it. It was great back in the day, it shaped a lot of modern day FOSS culture but now it's just MS.
In a reductive sense, yeah it's a bit silly. But zooming out, I can understand. Sucks to have your hand forced. Sucks to be let down. Sucks to watch something that was great fall from grace.
Thanks for Ghostty, been my daily driver for awhile now. Hope the rest of your day/week goes much better!
Bud. Right decision. Time is a forward moving arrow. You gotta do what's right for the project and over the years I've rarely seen your decisions going against the stream.
I feel this way, although less emotional, with Unity.
Unity taught me how to program and , along with JavaScript turned me from a college dropout to a software engineer.
Finished my degree later.
I still love Unity, but the company is stable. If I friend needs help with a Unity project, I'm down, but I start all my new games with Godot.
I'm not sad though. Unity is like a friend I'm still cool with, we just drifted apart.
But from a realistic point of view. Did we really think Unity and GitHub were charities in pursuit of the greater good.
Of course not. They cashed out, made money and whatever good they did along the way was a nice side effect.
I don't know why but I don't want to make fun of you. Just sad you can't enjoy it anymore.
This post reminds me of Linus video on Git, calling Subversion the most stupid project because it was.... Centralized. ;-)
"Tech Talk: Linus Torvalds on git" - https://www.youtube.com/watch?v=4XpnKHJAok8
"I'm not going to force you to switch over to decentralized, I'm just going to call you ugly and stupid. That's the deal."
If you choose something self-hostable (whether hosted commercially for you or no is of no relevance), I'm very interested to hear about it.
hug
Thank you for your hard work.
> Its given me so much and I'm so thankful for it. But, it's not what it used to be. I don't know.
Mitchell, when I was in 10th grade and had to pick my streams which led me to pick comp-sci/stem rather than finance (I am going to college soon), I thought of my dream life and it was being on a vacation/beach using Linux or terminals and opening github and contributing to open source software. I simply couldn't imagine my life without terminal (funny because ghostty is the terminal that I use)
You said that you have been with Github for 18 years, that is longer than the time I have been on earth. You were (and in some sense are!) living my dream life in that sense and github fulfilled its role, it had helped you until recently when it has started to get worse and worse.
my point is you have an special bond with github and for good reason,so to remove an somewhat integral part of all of this (github) after so long will have emotional feelings and outbursts.
I hope that you are doing fine, Ghostty/your-work has a positive impact on my life and gives a hope by being a relaible tool I rely on, I wish nothing but the best for Ghostty and you personally.
Throwing out this idea, but would you ever consider making your own version of Github?
Hey bud, thanks for the honesty and I feel your pain! You're an incredible engineer and I've looked up to you (even though we are the same age) since hanging out at Kiip. Our tools should be getting better not worse. Hopefully your influence can be a canary in the coal mine to make some real change to reliability. -D
> I know this is ridiculously dramatic, but its the truth: I actually cried writing this blog post (tears hit my keyboard, I'm embarrassed to say).
> I'm sure folks will make fun of me for this. It is a stupid thing.
Brother, it is not a stupid thing. We need more in the world of what you are doing here. Never change on this count.
Dude, get some help
It's not a stupid thing - GitHub not being serious about basic reliability is, at this point, a big risk to people depending on it for change management, much less OSS projects needing it to do every aspect of work in the public.
GitHub made working in the open a joy. It's very sad the state that it's in.
Bruh you're exceedingly wealthy, you'll get through this.
> GitHub only gets better if people who give a shit stick around to make it better
Quote the opposite. We need to leave so they receive the message in order to fix it. As far as the suits know, life is swell. So much so they can't keep up with demand. Be sure to say why you are leaving too, so they know what to fix.
Is this you moving a git repo to another git hosting service?
No serious person would make fun of this emotional reaction. It seems technology had something going on, and it quickly got flooded by incompetence and greed.
We have all been deeply involved, constructed careers and sharpened our tools with technology and hopefully for the benefit of technology. I can only imagine how deeply sad the current state of software is for those talented individuals that helped to carry it to here.
Some of us can at least hide it with cynicism because there is not much at stake, but emotional honesty is very much appreciated.
chill dude
the acquisition by microslop was the death knell for gh.
"They're your feelings and no one else has the right to how you should feel about them."
Damn GitHub is at a new low. I wish GitHub wasn't overtaken by the AI agents and hoped that the situation would improve. But it just didn't and ever since Microsoft took it over, it was just run into the ground.
I thought that GitHub was so unreliable that it would be better to self host instead of use the service [0]. It turns out that 6 years later, that was the case and it doesn't sound crazy anymore.
The problem is GitHub was neglected and the AI agents ran it into the ground and we need to now self host.
[0] https://news.ycombinator.com/item?id=22868406
Github won't shed a single tear in return, hell, they probably didn't even know until this came out. And not to sound harsh, but they probably don't care either. If they don't 'find their way', then there are 10 different competitors ready to take over, and I hope some of them do. Better for the ecosystem to have a strong element of competition. Perhaps their time as top dog is ending, and it's only natural, nothing lasts forever, especially in tech.
You have been a tremendous influence on my professional life. Vagrant made VMs easy to use. You were very gentle with my Vagrant PRs. We disagreed a bit and I migrated some of those rejected Vagrant PRs into VeeWee. Then Hashicorp happened and I was over the moon. (Full transparency - not everything was perfect, I lost 50% of my Hashicorp equity which hurt real bad but that's not your fault, just saying there were ups and downs!)
This is all to say I have tremendous respect for you. Which is why I say:
You also have the resources to fix this. You not only have the resources and skill Mitchell, to make it happen - You know everything that it takes to be the CEO of a Billion dollar unicorn - you have the connections, you have the vision.
More importantly, Mitchell, you care.
Make it happen. You have done it a few times before. Do it again.
[dead]
[dead]
[flagged]
This is not good intentioned, you're a jerk, and it's 100% fine (and healthy) to care about things in life.
7 replies →
Tools can be frustrating. We can get emotional with tools we appreciate and we grew up with. But we should also learn to not focus solely on work efficiency. As you say yourself, this is unhealthy. You've labeled it, now work on fixing that unhealthy relationship with work, and with that tool.
Nobody should be in an emotional turmoil because they can't do a PR in a 2h window during a day.
We should all learn to take things more slowly, because our current accelerationist society is detroying the planet, and is destroying social ties.
Because, if you get that emotional from on a non-functioning tool... wait until you discover how our non-functioning democracies allowed for a genocide to happen in Gaza, for people in the south to be doing slave-work for our AIs to satifsy people in the north, etc
It really has been remarkable watching GitHub just crumble as an organization. There's a lot of discussion about why: the switch from being independent to being part of Microsoft, having resources pushed to Copilot instead of core service, the organization structure itself, a reliance on vibe coding, etc etc.
Regardless of the reason, it's undeniable that GitHub is facing some serious issues. The unofficial status page[1] tells a horrifying story.
I would absolutely love to get some insider perspective on this (if only to learn how to prevent it from happening anywhere I work), but I think it's clear to anyone who has been paying any attention that GitHub is a sinking ship and the only reason people haven't abandoned it already is inertia. Considering how much else is changing in software right now I don't think inertia is enough to sustain a company.
1. https://mrshu.github.io/github-statuses/
> insider perspective on this
I do not work at MSFT but I don't feel that I need insider perspective to understand what's going on. GitHub is being managed the way other services get managed once they're bought by big companies. Initially fine, then starts to decline, then eventually craters. Everything becomes the numbers game.
Microsoft, Oracle, VMware, CA (where software goes to die), Salesforce, the list goes on. Every once in a great while there's a good M&A team that doesn't fuck it up but that's sadly rare.
I feel like MS went out of its way to make a point that GitHub and NPM would be independent orgs that no longer had to worry about making keep-the-lights-on money. It was positioned as a benevolent acquisition for the good of the development community.
As so often happens, that didn't last long.
Nest was originally independent. Didn't take long for it to merge with the Google Home brand.
I'm sure there are countless other examples.
14 replies →
I'm afraid this is a form of reversion to the mean. Successful startups are made of exceptional people: the founders, the initial investors, the first employees, the first clients. But when they get acquired by much larger companies, they are necessarily diluted in pool of people that are more "normal", less exceptional. This includes the customer base that is more "normal" as well. Slowly but surely, the extraordinary product/service the startup has been developing reverts to the mean. This is quite sad, because it feels inevitable. I'd like to know how to avoid it.
4 replies →
Big companies usually buy other small companies for their users, once the users move to their platform, things change.
Slack has suffered the same thing under Salesforce.
This is a general observation, no hard data, but I find there seems to be a wall at 2 years after an acquisition. By 2 years a lot of the best talent leave the company entirely or go somewhere else in the company. Things can cruise along just fine for a bit, but as the institutional knowledge slowly leaves it gets worse and worse. Couple that with the bureaucracy and insanity of a global mega-corporation, the quality fades slowly at first, then it picks up.
3 replies →
Hey, you leave Creative Assembly out of this!
It's just beancounters doing what they do best, counting beans and screwing up what was previously alright.
1 reply →
> GitHub is being managed the way other services get managed once they're bought by big companies. Initially fine, then starts to decline, then eventually craters
Can you explain what you mean by this? Like what does "fine" mean? What, specifically in the management, is the "decline"? What does "craters" mean?
Wow. According to the current metric (87.25% uptime), github suffers a partial outage 3h/day.
https://onlineornot.com/uptime-calculator/87.25
In their defense, they dramatically "over"-report sev-2/3's (things like, avatar urls are not loading in saudi arabia), which makes their cumulative uptime look much worse than it is.
If you filter for major/critical outages, their uptime of core services in trailing 12 months all have two 9's.
https://isgithubcooked.com/?severities=major.critical
Also, a huge part of their cumulatively-bad availability story is copilot, which is a functionality (LLM inference) that most organizations have struggled to get two 9's of availability in for the last 9 months.
5 replies →
Some years ago I wondered how long will it take them to go they way sourceforge went. Once you grow too much without a proper leader, you will fall :(.
Sourceforge died in a very different way though. Bundling spyware/crapware in install packages for open source software was a serious breach of trust, and was pretty much the direct reason for mass migration to Github. Github is failing on the technical side, but they at least mostly have their brand value intact. I think it will still take quite a lot for a mass migration of the same scale to happen.
2 replies →
Comparing GitHub and SourceForge as if they were cut from the same cloth is laughable to me. SF has always been a wretched hive of ads and dark patterns.
12 replies →
> The unofficial status page[1] tells a horrifying story.
If it weren't bad enough, github often has issues when the unofficial status page doesn't report them, so the actual number is even worse.
> crumble as an organization
I think that is exaggerating things a bit... GitHub is alive and well, and they're hosting more and more projects each month. A few well-known projects leaving every now and then doesn't exactly spell doom for GitHub
Have those outages actually been blocking your work? Somehow I haven't even noticed, just seen complaints on HN. I'm not saying it's not real, just wondering where the gap is.
Yes, many times. Roughly once a week this year my team or an associated team can't ship changes because PRs, GitHub Actions, or some other associated mechanism is down.
A big part of my job is doing code reviews, and its very common that pages or diffs just don't load. Or PRs literally don't appear in the PR list, even though they exist. It's a daily occurrence to play the 'is my internet down or is GitHub just being shit again?' game.
Oh, and don't forget the cases where the diff view sometimes misses some files for unknown reasons. Both in the 'new experience' and the 'legacy view'. You just can't trust it as much anymore.
Mostly the Actions outages, but yes.
So what? People have to unlearn this kind of brand loyalty. Companies are not people and not your friends. They are in the business of making money. We need to be more aloof and simply use their tools when useful and not get emotionally attached. Most of the managers and likely the devs had a good deal. Good money, and if it collapses, people still have a good resume line and can move on. And we users can also move on. There are plenty of other service providers of code hosting and CI/CD.
All of that is revisionist history at best. GitHub was a pile a shit long before Microsoft bought it has everyone forgotten when it would be a coin-flip on any given day if the site was even functional?
GitHub was in the right place at the right time to be a success despite the fact it's a massively clobbered together mess.
While I wouldn't necessarily phrase it this way, there is a chart going around social media that tries to imply that GitHub had basically 100% uptime right up until the MS acquisition. All it takes is either 1) having been there or 2) a cursory search of HN to know that this is a complete fabrication.
They are mostly blaming their shift to vibe coding for their problems. https://github.blog/news-insights/company-news/an-update-on-...
Hm. I read that as saying that their users are writing more code with the assistance of LLMs, thus placing more stress on their systems. I do not read it as making any comment about their own practices.
5 replies →
literally zero nines of uptime lmao, do they win an award?
Even if you go service by service you're talking about critical things like `git` operations (literally what they're named for) at a single nine, and stuff that's pretty basic like static web hosting as only two nines. They literally can't even keep static webpages up.
I can appreciate Hashimoto's genuine feelings about Github, and the world of open-source software development that it opened for him and that he spent a significant chunk of his life participating in.
On the other hand, I can't help but think that some of this heartbreak would have been avoidable, if only he possessed more of the Richard-Stallman-esque attitude that non-free software is inherently suspect and unethical. Github has always been non-free software hosted by someone else, and run according to its owners' rules and for its owners' benefit, not ultimately the end user. This was true in 2008 and it's true today.
I've also used Github for a significant chunk of my life, often because I had to for my job. But I've never developed an emotional attachment to it. Indeed, I have long been annoyed that Github is someone else's proprietary software, that does what it can to structurally lock users into their platform despite being built upon free-software git.
I've never been able to love software that requires an email-based account and accepting terms of service and that doesn't work in Iran because the company that runs it obeys US sanctions law.
So without reservation on my end, I'm glad to see that ghostty is moving off of github to something else.
> Github has always been non-free software hosted by someone else, and run according to its owners' rules and for its owners' benefit, not ultimately the end user. This was true in 2008 and it's true today.
Yup. At KDE we never seriously considered GitHub. We always built our own git infra, and eventually landed on GitLab, after banding together with Gnome and a (generous and forthcoming) GitLab to convince them to move everything we needed from the Enterprise Edition to the free software Community edition.
I think we've had exactly one multi-hour git outage in 16 years.
GitLab cloud lost some of my projects. And it was (is?) quite slow. Props to those who can keep it running self hosted.
2 replies →
The centrality of GitHub was part of its appeal. It’s where you went to see where nearly every (obviously not all) open source project was being developed. Based on his post, the network effect was a large part of the draw and the reason he stayed despite reliability issues. A more federated set of git UIs will never capture the same feeling.
I have had my eye on these technologies for a while. Embedding the issue tracker and such in your git repo. Every day these make more and more sense.
- https://gitsocial.org/
- https://radicle.dev/
- https://github.com/git-bug/git-bug
I made the decision to leave Github a couple months ago when I retired and started heavily working on personal projects. I like the idea of radicle and used it for a while, but it's complicated to set up and maintain if you want to run your own seed node and pin your personal projects.
What I ended up with is a version of a static forge - Charm's soft-serve to host the repos and a forked version of the pico.sh pgit static site generator. I added git-bug integration to track issues in the repo and an alternative CLI to git-bug that works better when collaborating with agents.
A static forge site is very resilient to bot traffic because it only renders a limited number of commits, instead of pathologically allowing a near infinite number of URLs for bots to crawl.
https://kilimanjaro.io if you want to see what it looks like.
2 replies →
Exactly this. Even though I don't use git-bug anymore, I'm still a sponsor. I desperately want an issue-tracker-in-.git to become a standard.
Issues and CI are the only lock-in. The latter is legitimate because you're using someone else's CPU, but every developer has the tooling to "git diff" and write comments if we could just agree on a format.
2 replies →
They're all just value propositions. Is it worth my time and money? There ya go that's it.
It's not unlike the emotional drama I see each time Netflix raises prices (people get really upset about that), or video game discussion (the worst). If it's not worth the the value proposition, move on ... don't hang on / waste emotional cycles on Netflix or something like that ...
Granted I'm not a robot, I get the the emotional connection too, I think back to my early days in computing and I still fondly think of the now defunct manufacturer of my first PC, later the Windows 95 start me up commercials ... it was something magical.
This is orthogonal imo. There are plenty of services that work really well that are closed source
Agreed. His suffering comes from his inabillity to see the bad in closed source software. I lost my respect for him when he sold Hashicorp.
The thing you love has been bought by Microsoft. When things belong to a large corporation, they can (and probably will) drift off in some absurd direction, because in a way, the relationship is reversed. The thing no longer serves you; instead, the brand, the user base, the reputation, and the key role and function of the thing are put at the service of investors. In this process, you are demoted from subject to object; from an animal grazing on open grasslands to an animal grazing in a fenced-in pasture to an animal standing in a stall and being fed compressed pellets that contain bone meal from its own species for nutritional value. That’s why it’s important not to walk into the fences too naively, even if the grass there is fresh and lush.
This is fantasticly poetic!
Are you… explaining the effects of being acquired to Hashimoto?
During one of the x threads where Mitchell was (legitimately) complaining about Github, there were a couple replies suggesting that GitHub should hire him to be their CEO.
And I remember seeing that and thinking "huh... not at all a bad idea."
There is a specific kind of leader that can turn such ships around, and they are strong in their convictions, and aren't just "managers", but visionaries coupled with strong execution and power to attract talent.
I think a new GitHub will emerge and when it's just right, will grow like wildfire (like OpenClaw, or even GitHub itself did during the SVN and SourceForge era). And many are already trying to be that new GitHub.
The problem is that Github does a lot.
However, I consider that there is still not a great UI for the core service, in special for a complex project.
In the other hand, I bet jujutsu has the best basic take, and is still missing a good forge.
But how much of that do people actually need? Most users don’t use most features. The core MVP is not that big.
Does it do anything that GitLab does not?
With what I heard about GitHub Actions, the GitLab CI pipelines should be much better.
Not that I haven’t shot myself in the foot with GitLab pipelines on numerous occasions.
Xit has a better “take” on Git. Pijul & Darcs still have better fundamentals.
Unfortunately, naming things is hard, and JujitsuHub just doesn't roll off the tongue the same way that GitHub does. jjhub? forgesu?
14 replies →
Maybe it's time for fossil to get another look... It's effectively distributed code, wiki, and issues all using the same tool.
Every time Fossil comes up, people's big objection is that you can't squash commits. Personally, I'm fine with that - I tend to agree with Hipp that the repo history should not sacrifice truth for the sake of pettiness in the timeline. But a lot of people seem to disagree, which limits the audience for Fossil. I use Fossil for my own projects but I wouldn't expect it to become big like git is.
> GitHub should hire him to be their CEO
And then impose the same requirements that killed GitHub in the first place.
The problem is that what users want GitHub to be and what their owners (Microsoft) want them to be are disjoint.
If AI replaces software development the way that big tech company management wants it to, maybe they'll converge again. In the mean time, people want a git remote and they're getting an unstable host diluted with some flaky vibecoding bullshit.
Gitlab is pretty cool to be honest, and it’s generally underrated.
I agree, but it does have faults. Performance is woeful, and managing an on-prem instance is (literally) a full time job.
3 replies →
He would pull them away from co-pilot and the unlimited spigot of money that agentic coding brings, which is contrary to the best interests of Microsfot.
I'm still holding out hope for distributed and federated git forges. The only compelling reason for everyone to centralize on GitHub is collaboration on issues/PRs without everyone allowing signups on their self-hosted forges. That could be achieved without hosting every line of code everyone's ever written in the same crumbling infrastructure.
It'll probably never happen. But it'd be really nice if it did.
Jeremie (of XMPP) has a neat project, v-it, which uses atproto (Bluesky) to let people socialize their changes to projects. https://v-it.org/
It's a bit short of actual PRs, but in some ways, especially with agents, the lo-fi approach has some advantages.
1 reply →
> I'm still holding out hope for distributed and federated git forges.
Do you know that you can just send a patch via email (assuming you're not using the gmail web client)? You can even save the diff on some hosting website and send the link via any text medium.
2 replies →
> I think a new GitHub will emerge and when it's just right, will grow like wildfire (like OpenClaw, or even GitHub itself did during the SVN and SourceForge era). And many are already trying to be that new GitHub.
Really? I can only think of two: Codeberg and Sourceforge. Which are both great, but that's not what I'd call "many".
Gitlab? Three distinct codebases is quite a lot to be honest. Especially when Forgejo has the lineage of Gitea and Gogs in its wake.
7 replies →
Gitlab, Bitbucket, Gitea
2 replies →
Sourceforge???
1 reply →
AtomGit
Aside from outages, what really bothers me lately about GH is how slow the "app" actually is. Keeping a tab open on a PR status check burns 25-30% of a core on my cpu even when it's hidden. Reviewing large PRs has an awful workflow. Almost every diff page I load starts with "there's nothing here" then starts to load...
>It’s not a fun place for me to be anymore. I want to be there but it doesn't want me to be there. I want to get work done and it doesn't want me to get work done. I want to ship software and it doesn't want me to ship software.
Has anyone else shared this sentiment? If so Redmond needs to lean in hard.
this is an absolute killing blow for Microsoft if it gains real traction. You made developers your cornerstone eight years ago for nearly 8 billion dollars. you spent another 2bn on minecraft to clinch the deal with young developers and the code camp kids.
Youve lost the OS, and the server realm. Lose the developers, and youre on your way to becoming the Xerox of the 21st century.
> Youve lost the OS, and the server realm. Lose the developers, and youre on your way to becoming the Xerox of the 21st century.
This is a very HN take. MS is terrible or at best "second tier" on everything they do including gaming, they also lost the mobile race, they're very likely going to lose the AI race, but they'll still hold hostage of the vast swathes of average white collar workers with Office, people that don't care at all about technology as long as they have Word and Excel.
There's a reason why writing .docx was one of the first proper skills that Claude got.
> This is a very HN take.
It's something that Microsoft leadership themselves certainly seems to have believed at times. From "developers, developers, developers, developers!" to courting Linux-targeting webdevs with WSL to VSCode, they've done lots to court developers, sometimes explicitly professing it as a central part of their strategy.
I can't disagree with any of the rest, though. Microsoft's (anti-)competitive strategy has never been about excellence so much as positioning worse stuff to win in virtue of network effects and integrations.
> but they'll still hold hostage of the vast swathes of average white collar workers with Office, people that don't care at all about technology as long as they have Word and Excel.
I can't wait for the anti-trust lawsuits. M365 and O365 are already super shady in terms of being able to migrate out or be interoperable with other solutions. "Accidental" roadblocks almost everywhere.
2 replies →
Is this even an issue these days ? I thought GSuite was good enough for most office work for a very long time now ?
People have been saying that MS was becoming obsolete for at least two decades. And a few times, it did seem heading to obsoletion: first when Google Docs launched, and second when Windows Phone failed.
And yet we're where we are. MS is still one of the most important corporations. Perhaps the most important one if you only count enterprise usage.
FWIW I also think an underappreciated advantage is Windows Server (last I checked that was still rock-solid) and Active Directory. Lots of CIOs / CTOs would correctly veto a move off of these, absent a specific technical problem. This is really more of a "hard knocks" lesson than anything fundamental to operating system design or implementation, but: the two Linux shops I worked at got at least a little sloppy about the sudoers list, or got frustrated and gave too much access to a "shared" folder, etc etc, largely because the admins got fed up with all the Mother May-I-ing. It just seemed to inevitably turn into a mess; sometimes that mess is fun and even productive, sometimes it's actually unacceptable.
Even the research hospital I worked at had a proper SELinux setup on the Red Hat installations, but by-quantity most servers were CentOS and it was way more of a free-for-all than it should have been, e.g. I was the fed-up admin when I was really not qualified! I screwed up a lot. Not that big of a deal: this was research-related computing and deidentified data. All the clinical computing was Windows Server. That is not a coincidence, it is really a market difference.
As someone who hates Windows 11... I do like the core Windows kernel, and would much rather do IT on Windows machines than Linux machines. Windows NT is very fussy and a bit bloated, but a huge part of that is an admirable commitment to backwards compatibility; a lot of XP applications run fine on Windows 11, except DPI wonkiness. And Windows' driers advantage isn't just commercial support; the kernel is fundamentally leaner and faster than Linux at real-time IO, and better about cleanly isolating driver processes across privilege levels. Very broadly, compared to Linux I find administering Windows easier to navigate and harder to screw up, especially with handling user permissions. Surely part of this is what I grew up with, but there's also a values difference: a lot of Linux users like how low-friction it can be since the OS doesn't get in your way. I kind of like that Windows makes you turn an excessive number of disarming keys... even when I am frustrated by it.
It does make me quite sad that the only real general-use OS options are the apex of a 20th-century operating system family, Apple's version of that, and a truly 21st-century monolith-microkernel hybrid whose specific design is a mystery to public science.
3 replies →
> you spent another 2bn on minecraft to clinch the deal with young developers and the code camp kids
You think? They're still pushing the "native" Minecraft that isn't scriptable aren't they? And maintaining the fully moddable java MC against their will.
First time I've heard Redmond used as a metonym for Microsoft
Nope. I think all this is mostly virtue signaling and a bit of "GitHub derangement syndrome" in the water.
People are ANGRY about the AI boom impact right now and "microslop" is trending harder than "M$" back in the day.
MH had a weird ass set of Tweets a month or so ago talking about GitHub needing disruption and how the UI was bad. Now it's "Not fun anymore".
I guess you die a hero or live long enough to be irrelevant and shouting at clouds like Stallman.
Work at a company on GH Enterprise. Outside those recent major incidents and a few spots here and there we haven't even noticed issues. It NEVER comes up on engineering or leadership meetings as an issue or risk. Not a single time has GitHubs issues come up as an agenda item. Yeah, YMMV but still...
> People are ANGRY about the AI boom impact right now and "microslop" is trending harder than "M$" back in the day.
The writer of this blog post is Mitchell Hashimoto, and he has posted positively about AI, so that doesn't track at all.
The reason people are talking about it is because the decline is rapid. That's worse than the raw downtime. There's a sense that it will be even worse in a year.
I'm not a fan of AI everywhere but I have 0 reason to think this is from AI usage at Microsoft. Still, we talk about the issues a lot. We used to do our project management in GitHub. For whatever reason, projects don't work anymore. You can add an issue to a project and it won't show up. So we moved that part off of GitHub. That's too bad, I liked linking to issues.
If this happens enough, the only thing left will be hosting code, and we'll look at each other and go "we can do this anywhere"
1 reply →
> To the "Git is distributed!" crowd: the issue isn't Git, it's the infrastructure we rely on around it: issues, PRs, Actions, etc.
A suggestion: use git-bug https://github.com/git-bug/git-bug in addition to migrating to another forge like Codeberg. It saves issues, PRs etc in git itself (not on a branch - on a specially crafted ref). It offers two way sync with a lot of providers.
Other VCSes like fossil store issues alongside the repo. I think it's appropriate because in a sense, issues are part of what gives meaning to the code (like documentation)
git-bug is great but it doesn't handle PRs nor does it have a method for users without commit rights to submit bugs to the project. I know they're working on the latter (something with the web UI?) but until then you still need some kind of public infra for issue management if you want the general public to be able to submit issues.
I use it for my project[0] to keep issues centralized with the repo, but I still use Github Discussions as a pseudo-bug tracker to let random users provide input. If it's a bug I add it to git-bug and sync it to Github issues for public viewing[1], but if you want use bug reports that's not really going to work.
[0] https://github.com/stryan/materia
[1] Ironically I got this workflow idea from ghostty and mise, both of which require users to submit bug reports as discussions first and only generate tagged issues once an actionable bug is determined.
Maybe Mitchell will pull a Linus and, out of frustration, take a weekend off to write the distributed infrastructure for issues, PRs, actions, etc. around git.
https://radicle.dev/
The most important part of Linus' project was day -1, when he sliced off all the chunks of work that depend on solving open research problems.
You don't want to start your Saturday morning declaring an _action struct, then filling the rest of the day staring at research papers about the current state of fast homomorphic encryption.
It was 10 days, but that's fine too.
> Other VCSes like fossil store issues alongside the repo. I think it's appropriate because in a sense, issues are part of what gives meaning to the code (like documentation)
I was thinking about fossil in the context of agentic workflows the other day, after seeing a co-worker go all in on sort of shifting themselves to a TPM workflow, using a locally hosted kanban board (inspired by OpenAI's Symphony).
It'd make things easier to have everything shoved into the repo, other than that everything is now shoved in the same repo being handled by the barely constrained chaos monkey that is an LLM coding agent. Locking things down gets hard if it's got access to the whole thing there.
> Other VCSes like fossil store issues alongside the repo.
Technically the issues in Fossil are part of the repository, along with the wiki, code, forum, etc. They come along with every clone and (mostly) cannot be deleted from the historical record.
Items of Fossil that are merely "alongside" instead of actually in the repository include unversioned files, chatroom content, and users and access controls. (Not an exhaustive list.)
It's definitely time to turn these loose web features into a real program. I don't understand the desire to clone github as a website. It's demonstrably 10,000x more work to maintain github.com than a "github" command.
Even if you only used raw git with GitHub, it still wouldn't work. Pushing changes from my laptop would fail for hours when their SSO would break.
I didn't know of this, that special ref mechanism sounds really cool! Thanks for the protip
We've had trouble with git and repo's that have used non standard refs. It's all fine and fancy until we wanted to use some tooling that works with git, except it wouldn't see our unusual refs, and because they were non standard they were effectively hidden unless you knew they were there. So the migration work (almost) silently lost 10+ years of old work that was hiding away under those non standard refs.
What do we think is more to blame for GitHub's massive decrease in quality? I've heard the following theories:
1. Increasing amount of AI-generated code in their codebase, decreasing the quality of the service.
2. Bought by Microsoft, and their bad engineering culture has spread to GitHub.
Perhaps it's a bit of both.
Azure migration is the most plausible explanation I've heard. https://news.ycombinator.com/item?id=45517173
GitHub claims that AI development tools have caused a massive surge in demand in recent months. They need to scale by 30X to keep up with demand.
According to GitHub, Azure migration is the attempt at a fix/upscaling, not the underlying cause of the issues.
Addressing GitHub’s recent availability issues: https://github.blog/news-insights/company-news/addressing-gi...
An update on GitHub availability: https://github.blog/news-insights/company-news/an-update-on-...
9 replies →
Coupled with this (unsubstantiated but thorough) discussion on the internals of Azure, if even a fraction of this below-linked post is true, Github's abnormally-filesystem-intensive workflows would have wildly unpredictable performance and reliability forced onto Azure.
https://isolveproblems.substack.com/p/how-microsoft-vaporize... https://news.ycombinator.com/item?id=47616242
Azure also regularly has incidents due to capacity issues in several regions, so that many Azure-managed services also go down. Some of those incidents have been open continuously for many months now.
OMG I was a few FAANG-like companies. Most acquisitions failed due to the migration. It always played in the same way:
1. The acquired company was small company to the acquirer. 2. We need to improve scalability and reduce cost!
Then, they migrated. The new system was worse and didn't have parity. It was years. Customers were moving off. The project/product shut down.
I glanced at zhe thread you linked. And as I understand they are in the process of migrating, which will take more than a year still.
If that’s the case, then it’s not necessarily a problem with Azure itself.
I'd add a third point: record service usage.
https://github.blog/news-insights/company-news/an-update-on-...
We don't have a labeled y-axis so their record usage could be a 5% increase for all they're showing us.
1 reply →
It interestingly shows how a centralized system may just fail or become too flaky at unprecedented growth.
I suppose it's a bit too on the nose to point out that git is decentralized and itself doesn't really suffer from this, nor need it.
And yet GitHub has felt the most dead it ever did. Less quality contributions. Less feeling of community. All the open source projects are struggling.
They dont have a service usage problem they have a slop problem. Ban the slop and the platform will thrive
2 replies →
Yeah if those graphs are even vaguely accurate there's really only one explanation: vibe coders pushing previously unimaginable amount of slop.
I would not be surprised if Github has to stop offering so many services for free.
4 replies →
Well, it started just after the Microsoft acquisition, when AI did not exist, and coincided with news of Microsoft fully ingesting the GitHub team and forcing architecture and priority changes, and has steadily continued since. So idk, it’s a mystery. Maybe it was caused by the thing that did not exist when it happened. Microsoft just posted on a PR blog that it’s the thing that did not exist, and they’re famously truthful, open, and altruistic.
It's been on a downward trend before agentic coding took over. I suspect it's a mix of Microsoft culture and Microsoft infrastructure. It's starting to feel about the same quality as other Microsoft services.
Short aside, I have to rehost dotnet CLI binaries because their hosting infrastructure is so unreliable that it was causing CI failures regularly.
I suppose there's a reason that most Microsoft development shops tend to vendor their dependencies as a culture.
Gamedev being the most prominent that I have personally witnessed.
EDIT: Why are you booing me, I'm right.
It started being bad after MS.
It started being very bad when MS pushed for AI
It began pretty much immediately after the acquisition. There was an uptime chart making the rounds a while back, and less than a year in, the all green data points of pre-Microsoft Github turned to lots of red. I assume brain drain, as everyone vested or otherwise completed their contractual requirements and cashed out. And, Microsoft has never had a great reliability culture in their cloud services, so no in-house talent to effectively take over.
I would say uptime and UX/UI:
uptime:
Incomplete pull request results in repositoriesSubscribe Update - We are actively reindexing the remaining ElasticSearch indexes. Our priority is ensuring correctness and avoiding further impact. We are taking a measured approach to safely backfill data and will share additional updates as progress continues. Apr 28, 2026 - 15:58 UTC Update - After yesterday’s incident, we are investigating cases where /pulls and /repo/pulls pages are not showing all indexed pull requests. This is because our Elasticsearch cluster does not currently contain all indexed documents.
No pull request data has been lost. As pull requests are updated, they will be reindexed. We are also working on accelerating a full reindex so these pages return complete results again. Apr 28, 2026 - 14:51 UTC Investigating - We are investigating reports of degraded performance for Pull Requests Apr 28, 2026 - 14:17 UTC
#2 makes #1 a big problem. AI-generated code is fine if you have thorough engineering practices around it. Are they blindly merging in AI generated code without review? Maybe. Thats an issue of engineering practices, not of the use of generative AI in general.
Yeah, this is what I was going to say. These two theories are not mutually exclusive, and there's an argument that they're casually related
https://damrnelson.github.io/github-historical-uptime/
I'm curious if your graph had the number of projects its hosting shown as well?
Note: I'm a graybeard coming from SVN era.
GitHub took a massive hit in credibility when it got bought by Microsoft. We are a burned generation, we have seen the worst of Microsoft. This created a massive crack in the foundation of trust for most people.
Then Copilot happened. Some people dug how the training is done, and one GitHub employee responded by mail that every public repository including GPL repositories are included (the relevant Tweets are deleted unfortunately). The created crack has deepened. Some of us (incl. me) left GitHub.
As Copilot entrenched, Microsoft's product development practices and philosophy took over, and vibe coding started to be used by hordes of developers, GitHub's code foundations started to crumble. Add the big migrations they're doing & regressions they are causing on the UI now, and we're here.
GitHub's first enshittification cycle is over. Now we're starting the second cycle. The bloated, slow, entrenched hegemon's decay from relevance phase.
It'll be a slow decay. It won't fall in a day, but they golden era is long gone.
Any more context on the copilot training note? More pointers would be very interesting, but we'd need to keep in mind how many different underlying models were (are?) branded as copilot. I thought at some points the "copilot" model in autocomplete contexts was a finetuned GPT from OAI.
Re: GPL, there are other open access datasets of git repos that make some distinctions between copyleft licenses but those are older resources now.
1 reply →
Nah they must be actively moving infrastructure (to azure?) for the amount of outages they have
Not necessarily culture, it could be just forcing to migrate to azure that is not reliable, no?
Azure is not the best, but it mostly works. GitHub gets only 98% reliability for git operation component, reading and committing. This is the most basic component. The fact they are not on this 24/7 and it isn't fixed is the result of a culture (=what is prioritized, what quality is accepted).
I mean I know we all love to shit on azure, but I don't think it's partially unavailable for 3 hours a day on avg over the last 3 months?
Reading the write-up again, this really struck me:
It’s not a fun place for me to be anymore. I want to be there but it doesn't want me to be there. I want to get work done and it doesn't want me to get work done. I want to ship software and it doesn't want me to ship software.
Github is really Microsoft. The above paragraph captures perfectly what it's like to work in a big company like Microsoft.
When Github was a startup, it was both a tech company and a social media for coders and a real-life social scene (especially in SF, some pretty epic stories over the years).
Once Github was acquired, it was a countdown to all the soul being sucked out of it and simply a mechanism being left behind.
[flagged]
I'm happy that raw git + mailing lists works great for the linux project, but can the rest of us all agree we actually do need issues & PRs? And that it's super painful to lose all this context when platform hopping, or when the service unilaterally decides to deplatform someone?
So where are we going? Mitchell will be deciding for Ghostty. If github's current trajectory is anything to go by, everyone else will need to decide where to go sooner rather than later.
I'm worried that it will be a Babel scattering event and this open source superpower that github catalyzed (how to describe it?) will just evaporate.
I'm also worried that wherever we go next could have the same fate as github.
So what then? Radicle is the only thing that I've seen that could theoretically 'solve' the problem, though it still needs a lot of work: https://radicle.dev/
There will be disruption as people move to various platforms and then one will “win” by a small amount which will self reenforce until we have a new GH and the pattern will likely repeat.
Companies will keep using GH for a long time because they seem to be really tolerant of outages (and have a massive switching cost depending on how much of GitHub they use outside of git).
Smaller teams/solo devs much less so.
Isn’t really anyway to coordinate it ahead of time, it’s more an emergent bottom up thing than a “all devs agree to move to X” ahead of time.
tangled.org writes issues as atproto data that lives in a user's PDS which is one neat idea.
Radicle stores issue & PR data as git objects. This approach interests me because issue data is as important as the code so we should treat it with the same care as the code. I.e. a tamper-proof cryptographic chain, signed objects, distributed redundancy, well-tread management features like synchronization and packfiles, etc.
> I know I work at GitHub so that might sound heretical, but I promise it’s not controversial for me to say it. Very few people internally believe that PRs and issues are ideal primitives for the future of engineering. And there are a lots of us inside the machine exploring what comes next.
From GitHub's Staff Research Engineer https://maggieappleton.com/zero-alignment/
Honestly the arrogance of their workers are truly astounding. It also tracks that someone with little software experience would become GitHub's staff research engineer. Truly a massive signal that we can't let these companies lead the direction of tech in our country.
> I sit at the intersection of design, anthropology, and web development
How do these people still have jobs post ZIRP?
1 reply →
Where is the arrogance? and I thought talk/slides where interesting.
And wdym even mean "lead the direction of tech". Its just people trying to build a product based on their views/vision.
Others are free to build their own competing visions? and everyones free to choose the platforms that they use.
I’m Maggie and I’m a staff research engineer at GitHub Next. At least that’s my title, but I’m actually a designer. Or I was, back when that was still a separate thing to engineering.
Ah. I didn't think we could debase the title of "engineer" any further, and yet here we are.
The state of HN truly has fallen if people are questioning Maggie Appleton's credentials. Besides, she's working on GitHub Next, not the core product. Sheesh.
5 replies →
You weren't kidding. They're an anthropologist who went into design a few years ago because "it's not terribly employable" and as of less than 1 year ago was a "Lead Design Engineer at Normally"? This is GitHub Staff eng steering the direction of the concept of PRs?
1 reply →
Github released that split PR beta, so sounds like they are still thinking about the future which is moving towards small manageable PRs which are part of a parent ticket. That's a solid way to dealing with AI codegen bloat.
The arrogance of anybody, let alone a designer, thinking they could build something better than the foundations of software (and the modern world itself) is crazy.
I love it, but you have to deliver or else I will mock you :P
Great! I'll take my money to someone else who can handle the current state of engineering instead of wasting it trying to predict the future.
I'm very interested in where ghostty ends up - I wonder if they'll follow Zig to Codeberg?
It does seem like it might, in general, be a very opportune time for GitLab (or another host) to publicly step up!
There seems to be a lot of chatter on X recently about wanting an entirely new GitHub usurper that doesn't look like GitHub at all, but in the short- to medium-term I expect this not to gain a huge amount of traction because of the sheer cultural embeddedness of git + GitHub in modern day software development.
Would love to see it become more common for projects with sufficient inertia to host their own forge like GNOME or Inkscape do. Could be a service that foundations like CNCF or LF offer to their projects.
GitLab? We use gitlab for work. Its way worse in comparison.
Last week I encountered a bug where my merge request simply didn't show that I deleted a file. Apparently it's because my MR included the creation of a folder with the same name as the basename of the deleted file. Unacceptable for a code hosting platform.
Other than that I miss GH Actions, a clear ui (gitlab has way too many sub-menus), a responsive ui (gitlab feels very sluggish). And while we don't have the Gitlab duo activated, it still pops out regularly eventhough I can't use it besides closing it. ...and I don't even want to start with their issue buard.
It strongly reminds me of Jira in terms of quality, which is no compliment.
At least it isn't Bitbucket.
I think Atlassian and Microsoft are genuinely in a competition to see who can make worse software and still have customers.
3 replies →
Eh, I kinda hope not. Codeberg's latency even for just browsing is pretty bad (in my experience) and also is only sporting a single 9 of uptime [1].
I wish Codeberg the best, but I thought it was a questionable choice for Zig and feel similarly for Ghostty—doesn't seem like a strict improvement.
[1] https://status.codeberg.eu/status/codeberg
Well, that page took 13 seconds to load for me :/
1 reply →
Tbf its free software and the quality will go up the more people are using it and contributing.
2 replies →
Same here. I'm mildly optimistic tangled will go somewhere and be a viable replacement
Maybe Ghostty will follow Zig to Codeberg, but it doesn't seem like a fit to me.
> It does seem like it might, in general, be a very opportune time for GitLab (or another host) to publicly step up!
In what way(s)?
As in, to present themselves as the new defacto git host, capitalizing on GitHub's actual + perceived lack of reliability
2 replies →
This seems like a great opportunity for new platforms who are rethinking the OSS space to finally gain the traction they need to be effective. For a collaborative platform, quantity is key, and I am hopeful that someone who is interested in advancing the software space will become the new go-to. This isn't to say that GitHub hasn't been innovating, but at least from my perspective, the way we've used git for the past however-many-years has remained basically constant.
Some projects that seem interesting: - https://tangled.org/ seems to be building out cool and exciting ways to write and interact with code (and they're distributed on the ATProto! But notably that's not their core selling point) - Microservices like https://pico.sh/ and https://sr.ht/ feel like fresh air...
Love sourcehut and want to see them succeed, but their build service (despite having some very cool ideas like allowing you to SSH into your build container) is pretty barebones / lacking compared to GH/GitHub actions. You either get no task parallelism (all your tasks are in one manifest) or you get up to N=4 parallelism (you have four manifests). As far as I can tell, you can’t specify job dependencies beyond just “when this job finishes, trigger this next job by deploying a manifest”. No build caching, and artifact sharing felt like a kludge.
Thanks for the callout: we’ve been reimagining code forges by making them irrelevant with tools and tiny services like: https://pgit.pico.sh (static site generator for git) and https://pr.pico.sh (pastebin for git collab)
They are still a WIP but it’s on our roadmap to continue to improve.
Tried tangled, quite like the idea! The fact you can always switch to a self-hosted knot is nice.
I was looking to self-host forgejo but I didn't want to expose any SSH, and needing to be on a tailscale network just to develop also seemed flakey.
I'll stay on codeberg for now and check out tangled from time to time, because I think this is a good use of ATProto
I’d love see Tangled succeed because it strikes a good balance of UX and features. Sadly, there’s no clear pricing story around managed solution. They are also VC funded so they can follow the “journey of VC backed org” anytime.
I don’t know if it’s production ready yet, but tangled.org is a really interesting take on a forge and I’ve been watching it for a while. It decentralizes the centralized parts of GitHub in a pretty neat way. The biggest problem with forges that aren’t GitHub is people need to make and manage all these different accounts for each place they contribute (which almost certainly will lower the amount of people who do. Maybe this is a good thing these days though...)
Tangled uses the identity stuff from atproto which lets the important stuff (git, CI, etc) be decentralized while people only need one identity to contribute (and you can self host your PDS too). So nothing ends up being reliant on a third party.
I'm also closely following Tangled's development. Their two biggest weak points: lack of private repositories and ux design (which I don't have a problem with but I've seen many people mention) are both being worked on. Atproto is developing a permissioned data segment to the protocol, and Tangled just hired a designer. I'm excited for it.
>manage all these different accounts for each place they contribute
For me that's a minor problem. The struggle of working across multiple code forges or making my code available on multiple is syncing CI/CD, issues, releases between them. I don't have the energy to maintain multiple versions of a pipeline.
But a tangled account doesn't solve the problem of needing an account on those other forges. You just added one more account someone needs to make.
maybe, but tangled knots actually federate. you could contribute to repos on knot.ghostty.org and knot.tangled.org with the same account. no other platform permits one identity across instances.
1 reply →
I wonder if this is related to the pretty serious security incident about Github which got published today:
https://x.com/sagitz_/status/2049153195243372569
With malicious HTTP headers, any user could access any repo on Github.com, or on the Enterprise Github instance they might have access to. It's even worse than that because it's remote code execution on the Github server.
It seems like Github has been a mess since the Microsoft acquisition. Definitely feels like another multi billion dollar screwup in the making, like Skype or Nokia were.
Hopefully the incidents in the last few weeks are a wakeup call, and they start getting their shit together.
Not surprised, I think I was subconsciously waiting for this as Mitchell has been very vocal about Github on X. They killed a lot of developer goodwill, and I feel this is just a start of the mass exodus.
Good luck to the team with migration! (And here's hoping it's ersc :))
> very vocal about Github on X
I really wish an open-source developer of his caliber would also migrate to a serious microblogging service which isn't so openly hostile to truth and civility. Ending the sticky network effect of an evil service starts with its biggest, most prolific users migrating away.
I find the alternatives more likely to ban/censor than X. Bluesky is definitely not civil to those with the "wrong" opinions, despite what proponents of the service say.
I see your point, but the last few (services) that tried seemed to have become even worse?
It's not about the technology, it's about the people. The initial people on your network matter. The moderators matter too. That's just a very different job than writing and shipping code.
It's all about who you follow. My feed is mostly AI people, entrepreneurs and nerds. Some political stuff gets through, but otherwise, I'm glad to be back on X in the last few months (I left a few years ago in disgust over the insane politics because even nerds were only talking politics).
2 replies →
Keep your friends close and your enemies closer
I know gitea / forgejo will be a popular suggestion, either self-hosted or via something like Codeberg. Despite also being a GitHub user since 2010 and also "doomscrolling" issues for projects I am involved in, I do host a gitea for personal projects where I don't need the GitHub network effect. It works well and is surprisingly capable!
Having said that, I stumbled upon this curious blog post about a security issues in Forgejo: https://dustri.org/b/carrot-disclosure-forgejo.html
I migrated my entire workflow onto a personal GitLab instance after the whole "pay a fee to bring your own bags to the grocery store" GitHub Actions pricing shenanigans earlier this year.
Best decision ever.
100% uptime. 100% less stress with each of the product/pricing changes over the past few months.
Was also able to build my own GitHub Copilot equivalent that auto-reviews MRs interactively.
Highly recommend it.
i am opposed to using anything which is not single binary and not using a sqlite db for self hosted things which don't need to scale to millions of users.
Is GitLab pretty good these days?
I remember quite a few years ago it having its own set of problems.
Yeah, if you're hosting your own just use forgejo. Forgejo has a better governance model and is actually open source, not a corporate project that happens to advertise in open source. The distinction is meaningful.
1 reply →
I had steered away for a long while thinking it was subpar to GitHub, but it's really come a long way. Especially running it on a local network it's noticeably faster in every way than GitHub, and I'm able to build complex gitlab workflows with custom runners that are fully configurable and have effectively 100% uptime and no queues.
forgejo has been great for us. It scales remarkably far with the built in sqlite db also. Single binary, no deps. You ofc have the option to hook it up to a proper database server.
It’s a rails app from the early 10’s era think heroku dominance. therefore to run it you’ll need a dozen sidecars for things like redis or elasticsearch and others. it has all the fun ergonomics and bloated memory consumption of that stack as well. the all-in-one go based tools are probably better for a solo homelab style deployment (gitea etc)
2 replies →
Is it a joke? GitHub is not perfect, but it is mostly free and survives billions of commits every day. You don’t think We are all able to scale a service so well.
I don’t know, I love it. There are many alternatives like bitbucket, gitlab, but GitHub is still better overall.
I cannot say i love or hate it as it is just a tool, but i use github all day long and the reactions here seems exaggerated and dramatic.
What is confusing to me, is as a business I would happily pay GitHub for many many features that I pay others for. Maybe MS thinks its just a billion here, billion there, but isn't it so easy to capture these?
1. faster more configureable action runtimes so I can get faster builds 2. usable merge queues because the github one is a joke 3. some reasonable CI management and workflow debugging features
Founder of WarpBuild here: we provide faster runners (also cheaper), and have some niceties around debugging workflows like ssh-ing into them, observability etc.
re: #1, Blacksmith (https://blacksmith.sh) exists and it works pretty well!
It was four years ago that GitHub had major enough outages with their database that they had to issue a press release (https://github.blog/news-insights/company-news/an-update-on-...). Five months ago I was actually still recommending GitHub. Then a month ago I left the platform, because I couldn't get shit done anymore.
The alternatives aren't great. If any VCs wanna send a couple hundred grand my way, I'd be willing to start a GitHub alternative, if only so I could have a not-crappy place to host my own repos.
We did raise $4.5M recently to build exactly this: https://tangled.org
edit if any VCs wanna give me millions of dollars to start a GitHub alternative, I might be willing to maybe consider it possibly
https://disroot.org/ provides Git hosting (and email, cloud storage, and more). Their annual revenue is about $35k. There's no money in this.
> When I went through tough breakups? I lost myself in open source... on GitHub. During college at 4 AM when everyone is passed out? Let me get one commit in. During my honeymoon while my wife is still asleep? Yeah, GitHub. It's where I've historically been happiest and wanted to be.
I've never had such an obsession to a platform or an activity as this. Some might say this is unhealthy, but I admire folks who can reach this level of obsession in their craft. It's just a joy to read about for me
Not to defend Github, but I sometimes feel there are two Githubs that aren't related to each other.
> This is no longer a place for serious work if it just blocks you out for hours per day, every day
Do people seriously experience outage every day? I really don't know... it always has been feeling like a once-per-six-month thing. Do people have extremely complex Actions that I can't fathom?
> Do people have extremely complex Actions that I can't fathom?
Yes. Think CI jobs that test every candidate PR against a matrix of build targets, run fuzzing, run simulation tests, run bench regression tests, etc etc. Modern CI workflow automation has reached way beyond what a pedestrian can fathom if you’re not on the wave.
I remember visiting GitHub's downtown SF HQ sometime around 2014 or so... it was soon after they closed their first significant funding round, and years before they were purchased by MS. I had a friend who worked there as a very early employee. I was at IBM at the time doing AI stuff.
I remember saying to myself, "every single meeting room and common area in this building is designed around the consumption of alcohol--the long bar downstairs, the meeting room modeled after an airport lounge, the meeting room modeled after a smoking club, the meeting room / roof deck...
A year or two later they had that public "me-too" snafu (years before me-too) that led to a founder's resignation, a whole bunch of other people leaving, and then Microsoft acquiring the company. I wondered back then, is this the end of the company?
Perhaps so, but perhaps not... Here we are, 8 years the acquisition, only now lamenting a slow demise. That's a nice run for a startup acquired by a behemoth enterprise software company. With the exception of Redhat (which is debatable,) IBM had no ability to keep a software acquisition's culture, verve, or ability alive past a year or two.
it was kind of a miracle that it held together as well as it did pre-Microsoft. I think to some degree, they got lucky, and were able to coast on being in the right place at the right time. And then because they were so central they attracted some amazing talent who managed to keep the thing scaling up _despite_ the culture.
If Github were shut down, it would feel even worse than if Hacker News was shot down. I am github user 1520. Signed up a just few days after Mithcel on february 2008. I remember the early days sitting in a hotel lobby next to Chris Wanstrath and discussing a bug I found on github. Not ready to do the switch yet.
As a European user of github I've only had one two occasions of it being down. I guess we can just be lucky it got a better uptime while we are awake
This is not the large ElasticSearch outage they had on April 27, 2026. This blog post was written a week before that, so this was a different outage.
I have nothing to add to this. Comedy gold.
Luke Wroblewski posted this earlier today: https://www.linkedin.com/posts/lukew_small-taste-of-the-inco...
The shape of the curve helps make it a little easier to understand why availability has been so abysmal.
There's no Y axis. It doesn't mean anything. There could be a 10% difference since 2023 for all we know.
It is sad to see how far GitHub has fallen. Will also be interesting to where mitchellh takes the project, I imagine codeberg and sources are possibilities.
I looked up my own ID and GitHub join date from the API, all the way back in 2009: https://api.github.com/users/dueyfinster
I feel this. :/ It also just reminds me of everything we've lost in tech since the 2010s. When I used to put Octocat and Google stickers on my laptop and go to conferences every year and everyone was so optimistic and vibrant.
Mitchell on what he'd do if he was in charge of GitHub:
https://x.com/mitchellh/status/2036866220449030168
https://xcancel.com/mitchellh/status/2036866220449030168
I was expecting something more pragmatic than 'lean into AI even harder' to be honest.
GitHub needs to slow down with the AI shit and spend manpower fixing what's broken. Actions is a complete fucking disaster.
Also I have no idea what Pierre is but their website is horrible.
1 reply →
The big idea is all agentic interactions should critically rely on GitHub APIs. Code review should be agentic but the labs should be building that into GH (not bolted in through GHA like today, real first class platform primitives). GH should absolutely launch an agent chat primitive, agent mailboxes are obviously good. Etc. GH should be a platform and not an agent itself.
Why do I want that running on somebody else's computer? It's bad enough that most developers already rely on Anthropic or OpenAI. What value does a remote working repo add?
1 reply →
> Copilot revenue goes to 0 if GitHub burns to the ground.
That's not remotely true. I doubt most Copilot Business/Enterprise subscribers care about GitHub at all.
Inbe4 he will move to some agentic git product from vercel
People suggesting git bug and other solutions miss one important part that also makes GitHub sticky: They have an app, being able to look at issues on your phone, getting notifications and being able to review things there is worth a lot.
User 2882 here. What I know is that once a mass exodus occurs from service A to service B, the issues of service A that led people to leave it for service B will start to appear in service B as well.
Really feel this. Along with group chat (irc), GitHub is the best form of social networking I’ve ever experienced. It’s how my co-founder and I first connected some 6-7 years ago. It’s the real LinkedIn for devs, where the posting activity is the work itself, rather than posting about the work. A truly magical place, while it lasted.
This was good for me to read. I'm still on GitHub, but think about moving more frequently than I'd like to
Probably relevant: https://github.com/ianchanning/awesome-github-alternatives
There's probably a few more to be added there now.
On a much smaller scale (niche personal projects), I'm also planning to leave Github (probably for a local forgejo or even gitweb).
The vast majority of features GH offers are of no use to me. In fact, in the age of vibe coding, zero-friction drive-by contributions are a net negative. The UX has been steadily dropping for years. The recent abysmal record in availability and bugs is just the last drop in the bucket.
The writing was on the wall the day they were acquired. They had a good run, but those days are long over.
Everyone should have abandoned ship sooner, namely when they were consuming content for Copilot without permission. When it became obvious that pushing your code to GitHub meant giving it directly to Microsoft I stopped using it altogether and ran my own git/gitlab/gitea (I've changed approaches several times).
> past month I’ve kept a journal where I put an “X” next to every date where a GitHub outage has negatively impacted my ability to work2. Almost every day has an X
Is it really this bad?
I've seen people complain about Github, but I thought it was more of a theoretical inconvenience rather than a real practical one. As in, the uptime for a serious software company should be 99.9, but two hours down just today, and constant outages over the month that they noticed... that seems way worse.
Yes.
https://mrshu.github.io/github-statuses/
94 incidents in 90 days.
It's not always you see a status page so colorful...
Yeah, we use GH heavily at work (not so much GHA for critical workflows, thank god). They have an outage that breaks our git operations once a week at least. Like, webhooks not delivered, PRs not showing up, git operations not working, API issues… and that’s not counting GitHub actions which we only use for noncritical workflows
The downfall of GitHub is sad, having a centralized way to find cool open source software is amazing. I use the feed of what people I'm following are starring, tags and code search to find amazing and interesting projects, and I'm afraid I'll be missing out on great but hidden software since there is fragmentation when people leave GitHub.
And the search capabilities of alternative Forges are not the same (Mostly due to costs I assume)
Was hoping to see a point about full-on chutzpah at training AI without any consent on all code uploaded to GitHub, but alas.
Too negligible a problem. Service outages are much more important issues, and much less controversial.
You're not alone. At my company, we're now making plans to self-host our Git and CICD. I probably can't sell them on Gitea+Drone or Forgejo or another open-source solution (even though it'd suit us well), but we're still going to find a solution that isn't dependent on someone else's platform not sucking.
The writing was already on the wall when MS required logins to search code just 48 hours after acquisition
Outages aside, I have not put any serious work (of mine) on Github since it came out that they trained CoPilot on everyone's code without any sort of opt-in or details about how licenses were honored. I moved all my code, and I stopped doing the Hacktoberfests as I realized their incentive to have us all do it. All the good will I felt participating in FOSS was lost almost instantly. I still make FOSS and still participate in other's projects where I can, but I host my own stuff elsewhere.
GitHub needs a Sonos moment, after they launched their failed new app that made everyone angry and leave they got a new person in and I've seen them actively respond to issues on BlueSky with honest responses and not corporate fluff ever since while also turning the ship around.
https://www.headphonesty.com/2025/07/sonos-officially-appoin...
Those footnotes - "no, not that outage" - are damning.
2026 - when you have to specify which catastrophic outage was the straw that broke the camel's back and prompted your migration.
Come to the Gnu Savannah (jk) strange to see so many projects moving off GitHub. I always used gitlab, and only grudgingly had a GitHub, because that is where every project was. So while seeing people move off GitHub validates my choice to not personally invest in it, I can’t help but be a little sad that We are splitting across the different git providers.
All this because Microsoft won't sunset the crap that is Azure and rebuild something reliable from ground up. GitHub survived on Ruby On Rails - which was notorious for being slow at scale back then - and still managed to have better uptime than all the execs at Microsoft managed to do so far since its acquisition. What a shame.
GitHub has been stagnant for so many years now. There was an extremely brief period where it was actually good and innovative at the same time.
They've started shipping stuff again, but it's mostly not stuff I want.
Meta-observation: GitHub's quality is so bad that Mitchell has to clarify in his writeup which recent outage he is talking about!!!
microsoft destroyed github: they were careful at keeping classic web (noscript/basic (x)html) support for their core features... and after being bought, everything broke steps by steps.
Now, you must have a whatng cartel web engine to interact with most of the basic features.
Thx microsoft, again.
devs should start to leave microsoft github, but for a forge which respects the web (namely which has a web site, and which is not only a web app).
> During my honeymoon while my wife is still asleep? Yeah, GitHub.
I realize that everybody is different, but this still doesn't seem like the best of practices.
Upvoted for the username
Agreed. Tech-bros think this is a flex. But at some point americans need to recognize when they have a unhealthy relationship with work, and with consumption.
Because this is affecting the planet, our social ties, and everything else. And it's having impact on all of us indirectly
I didn’t read this as a flex. More a rueful admission of his connection/addiction to GitHub.
1 reply →
From a security perspective, centralization cuts both ways.
Large platforms like GitHub have strong security teams and fast patching, but they also concentrate risk. A single vulnerability or abuse pattern can affect a huge portion of the ecosystem.
Decentralizing critical infrastructure doesn’t eliminate risk, but it distributes it.
What It Means for Open Source, Infrastructure and Security: https://tux.re/forum/viewtopic.php?t=183
Is there any service left that will just host your git and offer issues and PRs without cramming anything else down your throat, especially automated help, LLM based or not?
Ideally with private repos for free or a modest fee.
Gitea doesn't count because they only want to sell hosting to large organizations. The pre MS github model for private repos was just fine(tm).
>I’ll share more details about where the Ghostty project will be moving to in the coming months. We have a plan but I'm also very much still in discussions with multiple providers (both commercial and FOSS).
what a cliff hanger!
As someone with similar warm feelings for GitHub, it's kind of sad to see the fragmentation but I have similar frustrations with the recent outages. Perhaps it's time to explore the idea of unbundling the social/discovery layer from the code hosting/dev tool so we can live between the myriad git/jj hosts but still do "social coding" together.
Have not had such big outage issues as what's described here, although I have noticed more stability issues lately. Is this worse while Europe is sleeping maybe?
Typically we see it when the US comes online, we’ll see 500s on availability across all of GitHub — either corroborated by number of active users, number of updates GitHub is pushing (being a mainly US company), or a combination of both.
Github is Microsoft. Nothing more needs to be said, and all of Microsofts products and services must be avoided like the plague they are. A lot of young people have not had the "pleasure" of dealing with Microsoft historically, when open source was a cancer, so I understand why they make the same mistakes that people did in the 90s and 00s.
Github has been all right for me because I don't do too much collaboration and I prefer not having to worry about the security implications. But it just struck me that I have my own infrastructure on Tailscale. I could probably just use Github as an alternate remote and use my own infrastructure to store the code. I imagine a gix + axum + maud should be able to give me my own git web host.
The existing open web hosts are just super heavy. 512 MiB minimum RAM and stuff is totally unnecessary though I have hundreds of gigabytes of the stuff. And then you need all these DSL YAMLs around and a job runner etc. I think I could probably fit the whole thing into a much smaller size. And I have kube running already so job management isn't the hardest thing in the world. Nightmare for SOC2 perhaps. I guess we'll see.
I think this is all home-forgeable now. The advantage of Github for OP was the social aspect, clearly, but I don't use it for that. And I'm a really late user 7,322,596 from 2014!
I never had any positive relation to Github. Free software should be developed on free platforms. So I very much welcome this. Fuck Github. Every single outage Microslop vibe codes is a good thing.
But it's very interesting to read about the author's very different perspective. User 1299 in 2008 is wild. His Github account could share the Radler I'm drinking right now with me.
I see that it's genuinely sad, but proprietary software and services make you completely dependent on someone else. If you want to rely on something for the future it has to be FOSS, everything else is a rug that will be pulled under your feet eventually.
> I see that it's genuinely sad, but proprietary software and services make you completely dependent on someone else. If you want to rely on something for the future it has to be FOSS, everything else is a rug that will be pulled under your feet eventually.
I'm with ya, but building services at the scale of Github, (even when it was a fledgling) requires resources and budgets that very few FOSS projects can even try for. So any replacement is essentially guaranteed to happen commercially.
The original git model enabled part of what was necessary for a fully distributed social phenomenon, but it didn't even go half way. None of the critical social aspects of Github were, are or will ever become distributed, now that a gatekeeper monopolist owns it.
If you want a true FOSS replacement, it's going to need to do at least an order of magnitude more prep work before launching. We've already seen what we get when somebody puts up a plain git server, and we've seen when a single company extends it to become social with a proprietary, non-distributed model.
A better future requires much, much more up-front work.
There's clearly opportunity for a GitHub replacement that can operate reliably at scale.
I support Forgejo and Codeberg, but it's not clear that its architecture can scale to GitHub levels.
Microsoft subsidises a lot of OSS development. Who has equally big pockets?
I think GitHub has completely lost the plot over the last year or so, I don't think the stuff I work on will leave any time soon but I'm slowly losing my patience with github.
The other week I spent about an hour trying to figure out why my actions jobs were just stuck on waiting and not starting.
For my personal stuff, I think I'm going to migrate to either my own selfhosted instance of something like gitea or codeberg, the juice just isn't worth the squeeze anymore imo for GitHub, even with stuff like free runners and pages.
I personally think this is mainly attributed to GH Copilot and I would love to know if MS/GH even makes a profit on it.
github failure is a live lesson of dysfunctional org. A business unit like github need a CEO.
From FreeBSD to Windows 2000: Microsoft’s Painful Hotmail Migration
https://archive.md/KZ0sy
Do not forget: "Embrace AI or get out!"
[1] https://www.businessinsider.com/github-ceo-developers-embrac...
https://en.wikipedia.org/wiki/Embrace,_extend,_and_extinguis...
I really like forgejo, but for OSS it's a complete no-no unless they want to manage PRs by email. Maintaining a forgejo instance and allowing anyone to join is a recipe for headaches. Until forgejo figures out the federation aspect (allow to send PRs from other forgejo instances, or some other distributed way), it will be hard for OSS to adopt them and keep the collaboration aspect.
Why is it a no-no? Arent FOSS projects like Gadgetbridge or Forgejo itself using their PR system?
github is very disappionted for me, copilot usage changing is awful
> I'll share more details about where the Ghostty project will be moving to in the coming months
So in response to GitHub Issues, PRs, etc. being occasionally inaccessible each day, you're going to make them inaccessible for months?
Feels like a knee-jerk emotional decision, one that doesn't serve you, Ghostty, or the community.
At least have your backup ready to go
I can’t think of anywhere that does those things better as an all in one package
I’ve done it with bitbucket, how has their uptime been?
I do hope something good comes out of it with new platforms competing to refine, innovate, and iterate on git hosting and the UX of it all.
Is there anything less important than the origin URL of a Git repository?
I read this and felt like I was reading a moltbook post.
Am I an agent? Are you?
Is Claude... God?
A remnant of the old GitHub still remains, try surfing to a non-existing repositor like https://github.com/NowIsTheTimeForAllGoodMenToComeToTheAidOf...
(however the parallax scrolling of the background is gone, maybe when Microsoft arrived)
just use https://onedev.io/ !
best dev platform
Microsoft truly is the reverse King Midas!
Whoever made the decision to sell Github to Microsoft killed it, we’re just attending the funeral now.
Yes, I love their daily UX optimisations like showing issues comments in time ascending and having to click read more several times to get to latest comments. Each and every time.
why not just setting up github enterprise? i mean it's still an infra to take care but if you are willing to pay for it, you may as well? from my experience the other git forge doesnt provide the same feature sets and api as github, like gitlab ci is actually pretty limited compared to GHA, there is no concept of github apps for other providers too, but maybe you just want a code hosting..
We have both GHE as well as GH.com - and, i genuinely couldn't tell you which of the two blows up more often.
GitHub literally getting ghosted
Im still waiting for... Basically anyone that has used TFS (what microsoft had/pushed before acquiring github) to do a similar post, detailing how they miss the tool original concept. I'm sitting down, don't worry about me.
> TFS (what microsoft had/pushed before acquiring github)
It's still around. It's just called Azure DevOps now. I personally think it's great for what it does.
What are those strengths? I've worked with projects hosted on GitHub, GitLab, and Azure DevOps at my current job, and was generally not impressed with AzDO (mostly looking at CI stuff).
1 reply →
Help me out here because I honestly don't know / must have a different workflow.
Are other people being impacted every day by github outages?
What does that look like?
I'm not saying the writer is wrong, I'm just wondering how folks who experience this every day work / how that exposure plays out / what it is.
prs not being visible because search is down, various ui elements not loading, pushes failing, merges failing, gha runs that fail with random errors or take forever to schedule
i literally do not recall the last day that passed without someone on my team noticing that some portion of gh was degraded.
I've been impacted once: An action that failed to start (a PR check), then the merge button on that PR having no effect. Thankfully there was no urgency. It's a bit distressing because GitHub is kinda the engineering hub of the companies. We do have copies of the codebase on our computers and can launch build from there, but we have a process for a reason, and bypassing it is hacky.
the issue is where to go?
codeberg, self-hosted forgejo, gitlab, still-beta sourcehut, tangled? github was “the git community” and now it’s fracturing—you need accounts everywhere, you can’t easily discover neat projects
i like tangled if only because it’s built on atproto which emphasizes ownership and transferability of identity: something that would make the move off github so much easier
n=1 but i don't really discover new projects via github, it's mainly here, reddit, or via colleagues. then again, i selfhost forgejo so don't have a real presence on github
One of the issues is that Github competes with Azure Devops, and MS prefers to push Azure.
This comment doesn't add anything novel to the discussion, but is worth adding I think because hubbers and MSFT folks read HN - I too am evaluating leaving personally. Professionally, we're talking about it loosely, and if it continues it will become an increasing likelihood.
Just checked and I'm Github user 2,040,833
https://api.github.com/users/<username>
Thanks mkw5053
Is "migration to azure" or "microsoft acquisition" a cause or a symptom?
I'm wondering to what extent the natural life cycle of SaaS products comes down to: the company grows, the old guard with good technical taste move on, bad technical decisions are made, quality declines, users move on.
GitHub has a north star now, it's called "Embrace, Extend, and Extinguish".
https://en.wikipedia.org/wiki/Embrace,_extend,_and_extinguis...
This is assigning an unearned malicious competence to Microsoft
It's odd. I've been having the same feeling as well. Earlier this week, they sent that email about copilot, which I don't use but pay $10 a month for and I canceled my subscription.
GitHub has become a place where you seek people’s attention. There are other places you can freely host your projects. GitLab was always available. I just haven’t logged in for I don’t know how long. An open source project is essentially a show window to the internet by a lonely developer. Ghostty has already established a great community. It’s already on display on a skyscraper. The project is mature enough that it needs a dedicated discussion forum or something like that. I am excited to see where it will find home and how it will evolve.
i would be very interesting seeing how the dev space will look in 5 years from now, and how would github look in 5 years from now
>i have stopped opening github, i just use github cli heavily, that's it, gh gives everything i need out of the box
on github actions run on github and agent pull them, checks the issues and fixes the code, the whole workflow changed
If Atlassian had vision they'd swoop in with a sponsorship offer for Ghostty that included moving it to BitBucket.
Possibly in a few years from now we'll get actual data about how many outages we've seen or how much have x services degraded, overlapped with the push for "AI everywhere".
One can only hope that as people get tired of Github and move to other services, we'll see better Mercurial options. I feel like git itself mainly gained in popularity because of Github.
Either way, the thing that irks me about the Github situation is that so many people joined Github specifically because it was "where everything was happening". And now they realize that having one place where everything is happening is not really a great situation if that place starts going south. We need a range of providers with good interop rather than centralization.
An obvious pivot would be to Codeberg. Is there some missing feature there rendering such a move less desirable than I imagine?
Imagine if MS just did a git revert all the way back to ~2020. That was peak GitHub for me. We got some niceties the first couple of years after the acquisition - free private repos, Sponsors, secret scanning, a new mobile app and CLI - but things were still pretty stable, before their architecture and the little UX touches got destroyed.
What a timeline that would be. One can dream.
[flagged]
Anyway, good luck with the migration. Curious where you land. And honestly? Props for actually following through instead of just complaining on Twitter like the rest of us.
's been dead since microsoft acquired them in 2018
Is it really the case that GitHub had fewer issues in its early days? Or have our expectations just increased as GitHub has effectively become a critical piece of infrastructure? Go back to 2010 and half the functionality that people are complaining about (e.g. actions) didn’t even exist.
The author is entitled to his feelings. People can host their projects wherever they like. However, this is also a huge drama about basically nothing. GitHub is actually much more useful now than it was in its heyday (when it had far fewer features to go wrong).
> I want to be there but it doesn't want me to be there.
This hit me pretty hard. I hope GitHub finds its way sooner rather than later.
We are finally getting closer to me getting to delete my last account with Microsoft. Nixpkgs: please follow suit.
OP takes issue with GitHub's constant outages and alludes to agents (and Copilot bloat) as the primary cause.
Lots of big services are like this. Google Colab's 'Connect to Drive' is down as we speak. I'm up right now because I know my Runpod VM in Kentucky is going to die rather abruptly and I'll need to manually get it up.
Everything has its flaws.
Microsoft lets you host your code, websites and media for free and
Even if your analysis was correct (you're hyper-focusing on the AI stuff), "Lots of big services are like this." is not an excuse.
OP says he's been using Github for 18 years, but he's only leaving now. I think this is enough evidence things have gotten worse.
Are that many companies really using github? None of the handful of companies I've worked for have used a public repo.
there are plenty of enterprise github users. Where I work currently has an internal github and uses external github.com to host public facing OSS work.
"The timing of this is coincidental with the large outage on April 27, 2026."
This PS is as impactful as the body of the post.
about to launch my first open source project in days. reading this with a knot. github used to be a default; now it's a decision. and watching mitchellh agonize publicly is the honest preview every new maintainer gets from now on.
The question is where do you go?
Best alternative list anyone?
I think this Twitter question and response (from the author) is helpful to understand the problem:
Question:
So, I'm also annoyed wit GitHub's stability (especially lately), but I'm curious: Ghostty has only a handful of PRs per day (excluding robot contribs); how is this a real problem? (and yes, I read your blog article).
Response:
1) The robot contribs don't auto-close if GH is down (cause it relies on GHA). We have retries but its pretty annoying.
(2) A PR isn't one and done. We need to comment, we need to run tests (~80 per run), and we do this multiple times per commit (due to review back and forth). So one PR has a lot of GH reliance right now.
(3) PRs tend to batch up, e.g. we don't do PR review constantly because all of us have other things to do, so we usually will try to review/merge multiple at one time. 3 PRs per day = 20 per week, which is a ton for volunteer time!
(4) We try to coordinate merge parties across maintainers in China+US+EU and if GH is down during our small time slice we just can't do any meaningful merging for 24 hours. We could alter our process here but that's just gaslighting.
(5) We get an order of magnitude more issue and discussion comments, which are affected by all of the above except CI. These are particularly affected by GHA/API outages.
(6) Dev work by maintainers happens in non-PR branches that run CI, and if CI is down we can't test our code (since Ghostty relies on a lot of testing we can't run locally, e.g. for platforms we don't have). It effectively pauses work on that branch.
(7) I've had multiple days in that 30-day window where Git operations themselves failed for different reasons. So I couldn't push a branch or whatever.
It just all adds up to be WAY too work impacting. The Ghostty maintainer channel is a stream of "oh GH is down again."
Read the piece waiting for a diatribe on MS's unethical practices, left with an uptime complaint. Ok, if that is what it takes for people to move away from them, we'll take it.
Maybe you could start a new github - create the job you always wanted!
i empathize with the folks running a largely free service who are being spammed by bots and built everything around some other assumptions
Copilot showing up unbidden on my PRs was the final straw for me. Well, actually, the final straw was not being able to figure out how to turn it off.
We all saw this coming when the Microsoft acquisition happened. They constitutionally can’t not fuck their products up.
pack it up. we're going to codeberg.
What I want to see is Linux kernel leaving GitHub...Always had a bad feeling about it being hosted at somewhere controlled by Microsoft..
Linux kernel source is hosted at https://kernel.org , not GitHub. You're probably thinking of Linus Torvald's read-only mirror[1].
[1]: https://github.com/torvalds/linux
Thanks for the correction.
> Lately, I've been very publicly critical of GitHub.
Well, he is not alone with that. Something isn't working - and Microsoft either does not realise it, or does not care. I think the microslop strategy consumed Microsoft internally; it seems unable to change trajectory now. It's like you are driving to a cliff, in a car but you are not the main driver. It's quite interesting to see though - people can now expect "which disaster will hit Github tomorrow".
On the other hand, I also think it is time that Github gets some serious competition. Gitlab is not that competition; codeberg also not really (they'd need to up the useful features by a LOT and keep on driving that - I just don't see they have enough energy and momentum for that, but as a smaller source code hosting platform they are not bad either).
What does Gitlab need to do to be that competition?
If I was OpenAI / Anthropic, I would see this as a massive opportunity.
I mean, why wouldn't you want to consolidate git repos, a heroku/fly.io/vercel like container system and direct access to web-based coding tools. They have the coding models and agents, slap a web interface over Claude Code running in a container, allow for commits and deploys. Control the entire stack.
Sadly I feel the same way towards Windows.
I, honestly, do not care about Github. As just a career dev it gives no utility except that a lot of the open source projects are on there.
> To the "Git is distributed!" crowd: the issue isn't Git, it's the infrastructure we rely on around it: issues, PRs, Actions, etc.
Yet again, I wish the prevailing SCMS were more like Fossil, where issues and forum posts, at least, are part of the repository (and everything lives in a single sqlite file). (Of course Fossil actively opposes "pull requests", separate issue)
> (Of course Fossil actively opposes "pull requests", separate issue)
Not opposition, but very little incentive for the primary developers to implement the feature. Fossil's own developers happen to be the same as SQLite's developers, which doesn't accept outside contribution as a policy. It results in Fossil's features being predominantly, but not exclusively, the same features needed for SQLite and little else.
This thread discusses avenues for implementation: https://fossil-scm.org/forum/forumpost/ce238fccfd6b124d
what exactly is going wrong with github aside from all the outages in the past x months? i honestly don't find it particularly disruptive to work/personal stuff. excuse my ignorant, maybe i don't use github enough to know what causes this fury...
fwiw - i do keep a fair amount of code in my computer. i don't push everything..
I doom scroll GitHub issues too. :( I'm so addicted to open source hahahahah.
I'm GitHub user 191,754 (2010). Wow...
I reiterate gitlab > github
Bro was treating github like social media
>This is not the large Elasticsearch outage they had on April 27, 2026. This blog post was written a week before that, so this was a different outage.
Great footnote to finish the article.
Looks like removing the "meritocracy" doormat, hiring Coraline Ada Ehmke, and changing "master" to "main" paid off in spades!
<rant> I feel like this is the classic tale of corporate greed. Startups should stay startups. From the users perspective, I always hated the fact that you are the product. They create a great software, give you nice things, you fall in love and start to use the software, even advertise it in your circles because it's soo good. Then they sell the whole thing with you and your bros for big buck, and the new management slowly start to squeeze all the money out of it to justify the purchase while ruining the product. </rant>
It really has been infuriating lately. Between this and my company's proxy screwing with HTTP/2 at least once a day the frustration is very very real. While I'm nowhere as invested in GitHub its decline does make me sad.
Hear me out: Github needs ads . If option A is downtime (and data integrity issues), Ads are more favorable. The terminal UI and PRs are both captive real estate that developers have to pay attention to.
There is a simple cost equation of 40-100x demand vs a fixed op-ex budget for the org. Github can either 40x their paying customer fees or try to monetize all of the free vibecoder (and open source) traffic.
I thought that Ghostty was a company that had partnered with GitHub. But no it’s a popular open source application.
So they will move their CI and issue tracker somewhere else.
And this will be largely a springboard for “people are leaving the ship huh” and misc. GitHub demise discussions.
Related:
An Update on GitHub Availability
https://news.ycombinator.com/item?id=47932422
The unspoken reality of github: It would be significantly better both as a product and a vehicle in our economy if it was entirely worker owned.
I could recommend trying out source hut!
I find that so fascinating... I know GitHub since decades.
Over said decades I've worked on countless (open source) projects there.
Professionally? 1 project in all those years. Yes, exactly 1 (still there).
Every single other project was either in bitbucket, gitlab, gitea, forgejo or... I am sure I forgot some forge.
What I am trying to convey is: fascinating how "everything is on GitHub" is a very american way to see the world.
Ironically, I was thinking that the Github downtime is an American view in and of itself. For us living in the European time zones, Github is hardly down during our business hours. It's mostly down during US business hours, then demand is highest.
All of this and more entered my mind the very moment I learned that Microsoft had acquired GitHub.
I'm sensing a trend
I'm not sure how we ever could have expected GitHub to continue with or add quality when being built by the same company that also builds MS Teams. There are clearly the wrong quality levers at work inside Microsoft.
Yes, it seemed like Microsoft had a brief interregnum period of about 10 years where they seemed to have a renaissance and a genuine culture change and a concern for quality and initiative seemed to take hold.
And for many of us who came into the industry in the 90s this was a strange period because actually post-Gates/Balmer MS suddenly seem not so bad?
But that was until the first deals with OpenAI and the first round of layoffs. After Musk's purges at Twitter, MS was the first to really join in the fray.
Since then the old MS is back. Clearly as Machiavellian as in the past. But kind of sadder and more pathetic.
But honestly I'm also a bit confused by the framing some people have this thread because I remember GitHub always having reliability issues in its early days. It and Twitter were both famous RoR projects with notorious and constant outage issues in the 2008/2009 time-frame.
Teams has introduced substantial improvements over the past couple years..
Ah yes, after a decade of being one of the worst pieces of software with 10M+ MAU, literally only gaining market share because of monopolistic bundling practices.
So bad that if a startup had made Microsoft Teams they would've gone out of business after a year.
But the substantial improvements!!!
1 reply →
gh been going down hill since microslop took over. No surprise.
enshittification, as usual
Github was not built for a world where its userbase quadrupled and are pumping in generated slop at non-stop pace.
As a former user, I couldn't care less about their slop growth as I have no stake in them growing their slop.
It doesn't work if it doesn't work.
So not their problem.
Is their problem, but have some grace. You wouldn't be able to handle this insane growth either.
1 reply →
I blame Agent Smith
- Mr. Anderson
[flagged]
[flagged]
[dead]
tldr: chronic outages, near-daily github actions failures blocking real work
[flagged]
GitHub is fine.
As an aside, I always wondered why GitHub had a web interface. Admittedly I’m a pre-web SCCS/RCS “old timer” but I wouldn't have put a web interface on it at all.
Managing just about any complex service is far easier in a GUI.
It's targeted from the beginning to the masses.
It's used for non-technical people too; for documentation, dashboards, and bug tracking.
Viewing all this data is far easier in a GUI than a TUI.