Remix.run Logo
tedivm 10 hours ago

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/

_doctor_love 9 hours ago | parent | next [-]

> 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.

bsimpson 9 hours ago | parent | next [-]

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.

_doctor_love 9 hours ago | parent | next [-]

> would be independent orgs that no longer had to worry about making keep-the-lights-on money

It is honestly so shameful that we keep falling for this gambit. It is nothing more than a rank "but this time is different!"

Economics is what drives things. It is what drives things in households and it is what drives things in companies.

Unless times are truly great or the company is truly forward-looking, promises of freedom and independence from the business cycle is just an empty promise of creating a research lab.

jitl 6 hours ago | parent | next [-]

What do you mean "we keep falling for it"? I remember after the acquisition there were tons of projects that left for Gitlab or other forges on principle of boycotting Microsoft. And for the many who stayed on Github, we still got about 6 years of pretty great free services before reliability really started to decline.

And its not like Github's load stayed linear over the last 8 years since the acquisition. Repo creation and pushes went exponential about 2 years ago with the AI boom, so even with fantastic execution I think they'd still be struggling hosting the ever expanding archive of all code in the world.

layer8 8 hours ago | parent | prev | next [-]

I remember discussions at the time where people predicted that this would certainly happen. If people “keep falling” for it, it’s not the same people. And Microsoft certainly wasn’t (and isn’t) a company you’d trust for such statements.

bsimpson 8 hours ago | parent [-]

Satya got his own line of "maybe Microsoft's not evil anymore" press cycles out of it.

hansvm 5 hours ago | parent | prev | next [-]

> It is honestly so shameful that we keep falling for this gambit.

I'm not sure who "we" is in this story, but the _most_ optimistic of my peers pointed to typical MS projects of that scale having a little proper investment in interesting features and also taking at least a couple years to fail. HN sentiment wasn't positive either. The 99th percentile in favor of MS were fine with it, but the 90th percentile recognized the M&A for what it was, especially as specific features started showing their colours.

Lest this come across as a drive-by insult, I'm actually very curious who "we" is. Humanity is a very, very broad spectrum, and my intuition often doesn't appropriately capture the divers backgrounds of real people, despite spending large amounts of time with (usually from working alongside) deck-hands, captains, sanitation workers, bankers, pilots, jackhammer operators, semi drivers, farmers, programmers, mathematicians, and a host of other people. The gap I'm seeing is likely in my understanding (rather than, e.g., the post being mal-formed), so I'd like to correct that.

pdimitar 5 hours ago | parent | prev [-]

Who is "we", exactly?

Neither me nor dozens of my acquaintances fell for it. 100% of us said "GitHub is toast, it's just a matter of time". And we and many others were right.

Your "we" is misplaced.

jarjoura 4 hours ago | parent | prev | next [-]

GitHub had no reason to sell to Microsoft, they could have remained the bootstrapped company they started as, and rode the SaaS boom, since they were profitable on day 1. Seems a bit unfair to blame Microsoft though, because it was the founders who decided they wanted that sweet VC funding and Andreessen was happy to pay out.

Not sure if it mattered after that but they had that weird Tom Preston-Werner scandal that got him fired. Since he was the CTO, I kind of suspect that sent them on a collision course with needing to exit the VC round and Microsoft paid out.

wunderlotus an hour ago | parent | prev | next [-]

> It was positioned as a benevolent acquisition for the good of the development community. call me a skeptic, but can (and has) such a model existed in a capitalist system?

delfinom 3 hours ago | parent | prev [-]

GitHub was independent, and then AI happened.

All long term business goodwill and reputation is simply there to burn to keep the bubble going.

thinkingtoilet 9 hours ago | parent | prev | next [-]

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.

_doctor_love 9 hours ago | parent | next [-]

> I find there seems to be a wall at 2 years after an acquisition.

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.

znpy 8 hours ago | parent | prev [-]

> but as the institutional knowledge slowly leaves

I’d like to offer a different perspective: the “institutional knowledge” often (but not always, of course) are the old timers that have been gatekeeping knowledge in order to make themselves irreplaceable.

I’ve seen this a couple of times, even in faang-sized companies.

I’m not sure this is the case of GitHub though.

It might be due to lower quality code spit out by some llm, reviewed by some llm and shipped to production by some llm-generated pipeline.

Also, wasn’t github pushed to move to azure?

Anyways, it surely is a strong signal of engineering culture degrading.

theappsecguy 7 hours ago | parent | prev | next [-]

Slack has suffered the same thing under Salesforce.

superxpro12 9 hours ago | parent | prev | next [-]

Hey, you leave Creative Assembly out of this!

slopinthebag 4 hours ago | parent | prev | next [-]

It's just beancounters doing what they do best, counting beans and screwing up what was previously alright.

mvkel 6 hours ago | parent | prev [-]

> 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?

fabiensanglard 10 hours ago | parent | prev | next [-]

Wow. According to the current metric (87.25% uptime), github suffers a partial outage 3h/day.

https://onlineornot.com/uptime-calculator/87.25

gen220 8 hours ago | parent [-]

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.

simplyluke 4 hours ago | parent | next [-]

As someone who relies on it for all of my workflows at a normal job, core functionality issues result in me not being able to get work done on at least a weekly basis reliably at this point, and it's been that way for months.

The things aren't profile pictures not loading in saudi, they're botching merge jobs, git/api operations being down, pull requests not loading, etc. And that's on top of the plethora of UI bugs that have been pervasive for years that aren't blocking functionality.

fnordpiglet 6 hours ago | parent | prev [-]

Two 9’s? You have to work pretty hard to do that badly. That’s like bragging you graduated with a C average from Harvard after your father endowed a chair to get you in.

Given GitHub has become a utility service globally this should be frankly worrisome to everyone let alone the developer community actively using it. It’s intertwined into many things now beyond simply source code hosting and PRs. And I am surprised GitHub leadership is ok with the state of things. Having worked at a lot of 5-6 9’s shops, this would have been all hands on deck, all roadmaps paused, figure it out or perish sorts of stuff.

gen220 6 hours ago | parent [-]

Oh yea I'm not trying to defend it as amazing or tolerable, just clarifying the actual benchmark/reality of their performance!

I think at least three 9's would be the baseline. But I'm also sympathetic that they had a *post-exit* scaling of write volume of like, idk, 1000x???

Very few orgs would survive that kind of scale and retain three 9's.

unclejuan 10 hours ago | parent | prev | next [-]

> 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.

yetihehe 10 hours ago | parent | prev | next [-]

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 :(.

kivle 9 hours ago | parent | next [-]

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.

fnordpiglet 6 hours ago | parent | next [-]

Microsoft specializes in taking successful products and pumping them full of malware, spyware, bloatware, and adware once they have a critical mass of users. It is often preceded by quality dropping significantly due to under investment and McKinsey being brought in to find a way to prop up declining revenues - of course the answer is never to invest in making it a superior product again, but monetization strategies.

janalsncm 7 hours ago | parent | prev [-]

Mostly, but they were injecting ads into PRs if I recall.

pathartl 10 hours ago | parent | prev [-]

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.

SwellJoe 9 hours ago | parent [-]

Not always, but it was so long ago that it became that, younger folks could be forgiven for thinking so.

xstas1 8 hours ago | parent | next [-]

I do remember early SourceForge. It remember it as very clean, simple and reliable, and popular.

Steeeve 7 hours ago | parent [-]

Not popular. Core. It was the trusted place for open source software. Then it was ads. Then the day they bundled there was a MASS exodus. And the 14 people who ran their own source code interfaces scoffed and said "see. I told you." And we all said "yup" - we knew something would happen one day, but that was a worst-case-scenario that few thought was even a remote possibility.

bsder 4 hours ago | parent [-]

> And the 14 people who ran their own source code interfaces scoffed and said "see. I told you." And we all said "yup" - we knew something would happen one day, but that was a worst-case-scenario that few thought was even a remote possibility.

And nobody learned their lesson and they all piled over to the next centralized system that offered "FREE!".

And so it goes.

SwellJoe 2 hours ago | parent [-]

I mean, we got ~15 years of great service out of them for free. I used to pay for my own servers in colo for all the stuff Github has been providing for free all that time. It'll suck to move, but I've done it before. It's hard to turn down the loss leader they want to give me, when it's a really good product. Now that it's stopped being a really good product, maybe it becomes easier to turn down, I dunno.

pathartl 8 hours ago | parent | prev [-]

Idk, I'm in my mid 30's and I've never had a moment where I've been glad to see something on SourceForge.

SwellJoe 8 hours ago | parent | next [-]

So you were ~10 years old. I'll assume not a heavy user of Open Source software, at that time.

Edit: 2001, I see one (1) banner ad, and that ad was seemingly for an OSDN (Open Source Developer Network) conference. https://web.archive.org/web/20010517002942/http://sourceforg...

Given SourceForge only hosted Open Source software, and had no source of revenue beyond ads and sponsors for quite a long time, AFAIR, I think they get a pass on a banner ad.

tom_ 5 hours ago | parent | prev | next [-]

For whatever it's worth, which is probably not much, I'm in my late 40s and I never really liked sourceforge either. Too many clicks to do anything (still true), and I didn't like cvs (also still true, but thankfully now irrelevant).

(My SF account dates from June 2004. I expect I was thinking about using it as version control for a FOSS project I was working on at the time, though I don't know why, as it seems SF didn't support svn until 2005. Maybe I couldn't find any better options? The pre-GitHub ecosystem was pretty bad! But, luckily, I ended up not having time for any FOSS stuff from about autumn 2004, so: problem solved. And when I next looked, in early 2010, everything seemed to be git+github, and all the better for it.)

SwellJoe 3 hours ago | parent [-]

CVS was the best option when SourceForge began, and Subversion was barely an improvement. SourceForce was critical to the growth of Open Source and Free Software in the 00s. Projects no longer needed to maintain their own revision control server, file server, forum, issue tracker, etc. SF.net wasn't great compared to any of the current generation of hosting services. And, most Open Source projects were in an uncomfortable state of looking around for alternatives by the time Github arrived in 2008, because it was slow to adopt newer technologies and was running on a skeleton crew. Most of my projects had their own forums/issue trackers, and were self-hosting git, by then. Ads stopped being a usable revenue strategy, so SF.net stopped being able to keep up with what developers wanted.

But, it had a few years where every OSS developer I knew had nothing but positive feelings toward SourceForge. It gave one of the projects I work on thousands of dollars worth of transit over the years. It's hard for folks who've only ever worked on an "everything for small developers is a loss leader" internet to understand that we used to pay for and manage our own servers. I had a $200/month bill for just my Open Source projects on a couple of colocated servers.

Yes, SourceForge went through a lot of shitty stuff. The overtly hostile stuff (adware inserted in OSS projects) happened after it changed hands. But, when the revenue of their original model dried up and they couldn't stay on top of new development (being slow to offer a good git experience was a fatal mistake).

Anyway, it's not great now (though it is now owned by seemingly decent folks, who haven't really been able to find a way to make it work), and it went through a period where it was a borderline criminal enterprise, but it started out as a genuinely helpful part of the OSS community.

gurjeet 7 hours ago | parent | prev [-]

(To quote a famous TV series... :-) Oh my sweet summer child

tick_tock_tick 7 hours ago | parent | prev | next [-]

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.

jbxntuehineoh 9 hours ago | parent | prev | next [-]

literally zero nines of uptime lmao, do they win an award?

tedivm 9 hours ago | parent [-]

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.

pyb 9 hours ago | parent | prev [-]

They are mostly blaming their shift to vibe coding for their problems. https://github.blog/news-insights/company-news/an-update-on-...

valleyer 8 hours ago | parent [-]

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.

pyb 7 hours ago | parent | next [-]

Oh you're right, I misread. They're actually blaming their customer's vibe coding on their problems. I which case I call BS

Klathmon 6 hours ago | parent [-]

In our internal metrics you can see a clear increase in PRs and CI runs in general that tracks with agentic coding adoption, and it's significant, so I absolutely buy that GitHub would be struggling to take the brunt of that without big changes

jjayj 2 hours ago | parent [-]

But GitHub's postmortems are usually related to internal rollouts rather than traffic load

HDBaseT 8 hours ago | parent | prev [-]

[dead]