Top
Best
New

Posted by Nezteb 9 hours ago

Another GitHub outage in the same day(www.githubstatus.com)
271 points | 202 commentspage 4
rvz 7 hours ago|
A great time to consider self hosting instead. Since there is no CEO of GitHub to contact anymore.

A prophecy that was predicted half a decade ago [0] which is now more important then as it is now today.

[0] https://news.ycombinator.com/item?id=22867803

heliumtera 7 hours ago||
Remember the other day when a bunch of yous were making fun of zig moving away from GitHub? Now suddenly you all say this is not the future you wanted.

Everyday you opt in to get wrecked by Microsoft.

You all do realize you all could, for a change, learn something and never again touch anything Microsoft related?

Fool me once...

TacticalCoder 5 hours ago|
> You all do realize you all could, for a change, learn something and never again touch anything Microsoft related?

I learned that lesson in the 90s and became an "ABM" (Anything But Microsoft).

People sadly shall never learn: Windows 12 is going to come out and shall suck more than any previous version of Windows except Windows 11, so they'll see it as progress. Then Windows 13 is going to be an abysmal piece of crap and people shall hang to their Windows 12, wondering how it's possible that Microsoft came out with a bad OS.

There are still people explaining, today, that Microsoft ain't all bad because Windows XP was good (for some definition of good). Windows XP came out in late 2001.

Stockholm syndrome and all that.

skywhopper 7 hours ago||
This is the predictable outcome of subordinating the GitHub product to the overarching "AI must be part of everything whether it makes sense or not" mandate coming down from the top. It was only a year ago that GitHub was moved under the "CoreAI" group at Microsoft, and there's been plenty of stories of massive cost-cutting and forcing teams to focus on AI workflows instead of their actual product priorities. To the extent they are drinking their own Kool-Aid, this sort of ops failure is also an entirely predictable outcome of too much reliance on LLM-generated code and workflows rather than human expertise, something we see happening at an alarming scale in a number of public MS repos.

Hopefully it will get bad enough fast enough that they'll recognize they need to drastically change how they are operating. But I fear we're just witnessing a slow slide into complacency and settling for being a substandard product with monopoly-power name recognition.

ChrisArchitect 7 hours ago|
[dupe] Discussion: https://news.ycombinator.com/item?id=46946827
rpns 7 hours ago||
Not quite, that one is an earlier outage while this one started at (or a bit before) 19:01 UTC.

The history for today is a bit of a mess really: https://www.githubstatus.com/history

ChrisArchitect 6 hours ago||
They are all being discussed in that thread, the submitted url is just one of the various incident links on the day. Duplicate discussion.
rcakebread 1 hour ago|||
I'll bet you're fun at... nowhere.
esafak 7 hours ago||
No, it's a new outage -- that's the point! Check the URLs.
ChrisArchitect 6 hours ago||
That's not the point. The point is it's a duplicate discussion of one of a number of incident links being discussed, all over there.
bigstrat2003 3 hours ago||
The point is that when a second, independent event occurs, a new thread is not a duplicate.