Luckily we use gitlab instead of github
It also has some downtime now and then but it isn’t owned by microslop which more than makes up for it
I’m still trying to work out how to do ci tests without GitHub actions or a credit card or self hosting.
I understand it’s a joke, but really isnt the entire point of git is to be able to work locally as much as you want without affecting the remote repo and vice versa
For some reason tons of developers moved that amazing concept to depend as much on Microsoft cloud as possible for their workflows.
Git allows me to write code as much as I want. But GitHub does more than just Git. If you don’t remember the details of the next task you need to work on and GitHub is down, that’s a problem. As a senior I spend a lot of time reviewing PRs. That’s considerably harder when GitHub is down.
Sounds dumb to be that dependent on a US platform in 2026 AD
Right? We’ve had two thousand and twenty six years since Christ walked the earth to reduce our dependency on GitHub, what are we even doing
I mean there are tons of options in that space so if it’s an issue that is sorta on your business to have evaluated their dependency.
We work on an internal gitlab instance that has had 100 percent up time for like 2 years. It doesn’t even have to be gitlab, there’s gitea and like 10 other options.
I personally think that the industry has moved so far in the direction of cloud and saas that it’s lost a lot of valuable skills and made them dependent on too much externally.
It’s like “nobody ever got fired for buying IBM.” Nobody ever got fired for pitching a migration to GitHub. It doesn’t have to be good. Then one day it’s crumbling down and people will have to learn to face consequences.
GitHub has actions etc. a lot of people don’t build locally. They push to GitHub and it builds, tests, deployed, does checks etc
You should be able to replicate at least some of that locally. If you can’t work with GitHub down for a couple of hours, then it’s a poorly set up project.
Tell me you don’t actually code enterprise without telling me you don’t actually code enterprise.
You can still make a CI/CD pipeline that doesn’t self combust every 5 minutes lol.
Nah. If your entire dev team has to be on pause when github is down, you’re doing it wrong. Especially enterprise.
Sorry but that is just the reality these days. Instead of having local «it works on my computer» setups you have one place that builds
Off code you could run your own gitlab or whatever but it’s just cheaper and more efficient to buy a sass solution
Sorry but that is just the reality these days. Instead of having local «it works on my computer» setups you have one place that builds
You should have both. Having your entire dev team unable to work when one service is down is absurd.
Welcome to the world of SaaS I guess? It’s very standard. I mean GitHub used to have better uptime than you could achieve on your own.
It’s not cheaper if nobody can work for hours.
It’s possible to design your devex to require an unreliable SAAS vendor for even basic tasks! If you try hard enough you can logjam your entire team!
I don’t really get this joke as I’m not a developer but does it have something to do with that thing where I try to search the site and it tells me it’s getting too many requests from my IP, even though I haven’t searched it in a month?
GitHub is where a lot of companies store their source code, so many software development workflows require it to be available. For a while it had fantastic uptime, but since Microslop started shoving vibe coded updates its reliability has cratered.
GitHub manages not one, but TWO nines of availability.
Sometimes both nines are even in the front!
It’s reliability was already not super great before the vibe coding hit.
It’s mostly caused by them trying to migrate complicated legacy systems to azure. This type of work is already fraught with danger.
The vibe code just supercharges an already risky endeavor. The LLM code could be perfectly correct but the more dynamic a complicated system the more difficult it becomes to judge side effects of any one change.
The speed of change also means that experts in particular areas of the code base may find their mental model of the system to be out of date and incorrect faster than ever before. This is course also leads to the increased chance of mistakes or unintended side effects.
It’s been Windows 11’d and the regular patches of downtime are just one of several new productivity-loss features to be rolled out.
Next; ads.
…no, wait, that’s already happened.
Next; sponsors.
…actually, wait, that was kind of done.
Next; a bloat UI front-end to minimise the confusing layout. Subscription to opt out.
Nah, next is replacing all UI with a copilot prompt that always shits on your code and guilt-trips you when you try to look up some repo instead of just asking it to vibecode it for you.
codeberg was down a few times in the past days, but i feel like its got more uptime than github atp
At least codeberg isn’t a billion dollar company
deleted by creator
deleted by creator
