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.
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.
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.
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
My self hosted gitlab instance has better uptime over the last 12 months than a billion-dollar SAAS product 🤣
deleted by creator
deleted by creator