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.
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.
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.
It's called a vesting schedule. ;)
What I've seen is that usually the founders and heavy hitters from the original company are very BS-averse and basically just stay around to collect their money and then jet for a situation that doesn't suck.
For the rest of the gang, it tends to bifurcate: some folks stay at the big company indefinitely after the acquisition because while they can see the suck, nowhere else pays as well or is as cushy (I know people who have been thinking about leaving for 12 years). Still others excel at big company work and make a happy career out of it for a while but don't stay forever.
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.
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.
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.
https://mrshu.github.io/github-statuses/
94 incidents in 90 days.
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).
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.
Really? I can only think of two: Codeberg and Sourceforge. Which are both great, but that's not what I'd call "many".
I guess it's possible that my experience is wildly different than others, but if we're talking about volume of usage today rather than individual preferences, it's kind of shocking for me that someone wouldn't think to reference Gitlab at all in the list of potential successors, let alone not mention it literally first.
It'll probably never happen. But it'd be really nice if it did.
It's a bit short of actual PRs, but in some ways, especially with agents, the lo-fi approach has some advantages.
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.
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
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.
In what way(s)?
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.
I think Atlassian and Microsoft are genuinely in a competition to see who can make worse software and still have customers.
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.
Thanks for being human and making ergonomic software for humans.
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?
AI slop code
CV-driven development, a treadmill of features nobody needs that hurts stability we do need.
FWIW, some people used to (or still do) say similar things that software is significantly worse because people use "unserious" languages like PHP, Ruby, Python, JavaScript. It brought about so much cool shit that I don't think it's worth saying we should've stuck with only C and Java.
That's definitely great for work life balance, and I don't think any less of them for that, but passion seems to be gone.
I would be doing what I do for work if I was employed or not. That's how everyone I used to work with was. Now everyone seems to do the minimal, with the goal being more to direct blame than solving neat problems.
Used to be nerds hanging out on IRC, distributing Slackware, hacking trialware, modding games, etc. that had the passion and problem solving determination to do software work, which used to be harder due to lack of access to information.
OTOH what a great time for a budding engineer. I'm in my mid 30s, and no longer have the same stamina and passion as in my teenage/20s, but in the last 5 years I've learnt so many things I could not have done so back in the day. I learnt and experimented way more around random topics like compilers, OS, electronics, databases because of ease of access to information, AI (:shrug:), even though I have way less free time.
It's not a coincidence that every impressive result done using AI has come from someone with a track record of impressive results before AI. AI isn't magic. It doesn't make you good at stuff you're bad at.
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.
They seem to have changed the primary source of data in the issues and pull requests tabs (w/o filters applied) from the underlying database to the elasticsearch search index, which has the side effect that there's a noticeable delay between state change of an issue/pr and an update in the UI. But as seen today, these can get out of sync, and apparently they even had data loss in the index.
I would really like to know their reasoning for making that change. I can totally imagine that they wanted to "simplify" so the UI uses only a single data source instead of two.
As a user it's incredibly annoying to have a delay between issue/pr state changes and the search index picking it up.
When the outage happened yesterday I sort of figured it was something I had been noticing building up or something.
With that said, Mitchell complains about outages. These started directly after Microsoft acquisition[4] and are attributed to migration from AWS to Azure.
[1] https://github.blog/engineering/architecture-optimization/ho...
[2] see html source for tags
Yesterday we saw PR pages that displayed no error, just displayed wrong info. I would have preferred to get an error page than outdated or empty lists. I was guessing this was related to the React migration but I don't really know.
No AI needed at all. Only humans.
Companies know how to make good product, but if they don't have "new and shiny" to impress us anymore, then their only alternative is to make things worse so they can heel turn and then make things "better" by unmaking all of the worse things they did.
They can also milk their customers coming and going in the process.
It's not "enshittify or lose", its just raw greed. Things will get better again, either that or a competitor will destroy them. Enshittification is just the current meta and a new one will come soon enough.
I think it’s “find natural monopoly and reduce costs (aka enshittify)”.
Github is a natural monopoly and users cannot go anywhere. Unless you’re famous like Mitchell Hashimoto.
1. The company builds a moat and just remains shit.
2. New entrants either displace the company entirely (most likely) or competition slows the enshittification process (distant second) or reverses it (almost never).
It's not clear to me why "get shitty" is a necessary step to this. What part of GitHub's executives' grand plan is "have a barely-functional service that randomly prevents people from working"?I am not again performance bonuses, but they should be attach to better metrics. Eg the number of happy users is still up in 3 years time. Or something like this.
Another gigantic unspoken issue is that people have started building tons of stuff with React on purpose for some reason.
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.
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.
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.
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.
And boy, does it hurt.
I'd be absolute crushed if Linux (for example) morphed into something I could/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).
Ghostty will be fine wherever it lives because people follow the project and not where it's hosted. Best of luck!
> 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?
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.
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.
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.
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.
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.
It's a product that is _de facto_ present in nearly all developer scenarios. There are scenarios where I personally believe public management is better than private management, e.g. single-payer healthcare is strictly better than the bullshit we have in the US now. It's fundamentally cheaper for the polity when the government negotiates with healthcare providers than each private insurer.
I don't think that's fundamentally the problem facing GitHub, and I don't think it would be better in any way — for anyone — if it were regulated like a utility. But again, I write javascript for a living. Take what I'm saying with a big-ass rock of salt.
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.
Created at 2010-10-27T23:42:22Z. 16 years! What a wild ride. I used to use bitbucket a ton back then. I loved it.
Will redirect to an image file whose title is your user ID! :D
TBH I'm not super invested in github. I pay for it (smallest plan) and use it as a repository and for forking other projects occasionally, and for hosting some small-time static sites. I've never really needed any of it's other features. Every time I go to github.com there's more and more cruft though, which to me means that I'm not their target customer and they will inevitably either alienate me or jack up their prices. Happens every time there's an acquisition so I'm kind of used to it now.
Github has remained surprisingly useful for quite a while post M$ purchase, but I'm old enough to know that everything M$ touches eventually goes to crap. It's like a law.
I remember using CVS and Subversion though, with very limited hosted options, and I thought Github was the bees knees at the time.
ID: 67,498 Created: 2009-03-26
17 years, a month and two days ago.
When I was working at Microsoft I got transferred over to GitHub for awhile and someone there noticed my ID and made a big deal out of me having a 4-digit ID. :)
I never thought about it before then.
I had just tried asking Gemini to help me get there, and it kept telling me to read line 2 of github.com, as if they were serving JSON on their homepage. :facepalm:
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?)
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.
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
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.
Same :( their 9 5's is embarassing
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.
> 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.
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.
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?
That's not remotely true. I doubt most Copilot Business/Enterprise subscribers care about GitHub at all.
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.
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 looked up my own ID and GitHub join date from the API, all the way back in 2009: https://api.github.com/users/dueyfinster
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)
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.
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.
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.
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.
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.
I realize that everybody is different, but this still doesn't seem like the best of practices.
Because this is affecting the planet, our social ties, and everything else. And it's having impact on all of us indirectly
This PS is as impactful as the body of the post.
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)
And the search capabilities of alternative Forges are not the same (Mostly due to costs I assume)
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.
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 remember quite a few years ago it having its own set of problems.
I have nothing to add to this. Comedy gold.
https://en.wikipedia.org/wiki/Embrace,_extend,_and_extinguis...
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.
Issues, Pull Requests, etc, are all vendor lock-in masquerading as useful features.
An Update on GitHub Availability
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...
This hit me pretty hard. I hope GitHub finds its way sooner rather than later.
The shape of the curve helps make it a little easier to understand why availability has been so abysmal.
What a timeline that would be. One can dream.
arn3n•1h ago
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.
cdfalcon•1h ago
rstupek•1h ago
PunchyHamster•1h ago
It started being very bad when MS pushed for AI
celestialcheese•1h ago
Reason077•1h ago
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-...
dijit•1h ago
The issue is that they're not a scrappy startup anymore, they are defacto running the internets development infrastructure and are owned by a trillion dollar company.
So the bar they're measured by has changed and they haven't even tried to keep up, paying lip service to reliability when you are critical infrastructure is not going to go well.
There were reliability issues in 2010 for sure, but it feels worse now; the period before acquisition was the most stable (2014-2017).
vvillena•1h ago
omosubi•24m ago
plorkyeran•37m ago
dgb23•1h ago
If that’s the case, then it’s not necessarily a problem with Azure itself.
Nemo_bis•39m ago
btown•9m ago
https://isolveproblems.substack.com/p/how-microsoft-vaporize... https://news.ycombinator.com/item?id=47616242
mirekrusin•1h ago
alexxxxxxxxxx•1h ago
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
maxvisser•1h ago
carlos-menezes•1h ago
https://github.blog/news-insights/company-news/an-update-on-...
sureglymop•1h ago
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.
IshKebab•1h ago
I would not be surprised if Github has to stop offering so many services for free.
dgb23•1h ago
I‘ve noticed that some projects have „Claude“ as one of their top three contributors.
madeforhnyo•22m ago
nvme0n1p1•1h ago
They aren't, of course. The Y axis is missing. GitHub didn't have 0 daily commits at the start of 2023.
https://handsondataviz.org/how-to-lie-with-charts.html#exagg...
marginalia_nu•1h ago
weiliddat•47m ago
arianvanp•44m ago
They dont have a service usage problem they have a slop problem. Ban the slop and the platform will thrive
tfrancisl•1h ago
saghm•19m ago
campbel•1h ago
Short aside, I have to rehost dotnet CLI binaries because their hosting infrastructure is so unreliable that it was causing CI failures regularly.
dijit•1h ago
Gamedev being the most prominent that I have personally witnessed.
EDIT: Why are you booing me, I'm right.
bayindirh•1h ago
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.
spindump8930•1h ago
Re: GPL, there are other open access datasets of git repos that make some distinctions between copyleft licenses but those are older resources now.
bayindirh•54m ago
> Re: GPL, there are other open access datasets of git repos that make some distinctions between copyleft licenses but those are older resources now.
Arguably "The Stack" contains only permissively licensed code, but there are two repositories of mine inside it. One is a very simple logging library, without any license (which implies "All Rights Reserved"), and another is a fork of LightDM which I worked on, which is GPL licensed.
So any "permissively licensed" dataset probably contains at least one copylefted or strong copyrighted codebase, making them highly suspicious.
== EDIT ==
Found some. Kagi's date-constrained search to the rescue.
1. Should GitHub be sued for training Copilot on GPL code?: https://news.ycombinator.com/item?id=31847931
2. GitHub Copilot, with “public code” blocked, emits my copyrighted code: https://news.ycombinator.com/item?id=33226515
3. AI-Powered GitHub Copilot Leaves Preview, Now Costs $100 a Year: https://developers.slashdot.org/story/22/06/25/0334207/ai-po...
4. GitHub Copilot is trained on all languages that appear in public repositories (CTRL+F on the page): https://web.archive.org/web/20260428180443/https://github.co...
SwellJoe•12m ago