Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Days since last GitHub incident

github-incidents.pages.dev

Post reply on HN
Print view View original

31–40 of 142 posts

Re: Days since last GitHub incident

#31

Post by blibble »

behnamoh wrote: post #14
blibble wrote: post #10

Earlier quoted context omitted.

because Microsoft are known for listening to their customers? this trivial bug fix took more than a year to be merged: https://github.com/actions/runner/pull/3157 that bug likely ended up costing customers millions

Why is Microsoft supposed to listen? I'm not happy with them either but I understand their shift in business strategy. So many people here treat github like it's a utility; it's not. If you're not happy with it, move on to alternatives or make your own version.

> Why is Microsoft supposed to listen?

that's the point isn't it?

GitHub was a product that was loved by its userbase, because it was built by developers for developers

but Microsoft only care about one person, and one person alone: the individual that approves the purchase order

the people who have to suffer actually using the software are unimportant

which explains the rapid descent of GitHub into your standard quality Microsoft product (i.e.: terrible)

Re: Days since last GitHub incident

#33

Post by venturecruelty »

ZeroConcerns wrote: post #11

This is a bit... low-effort, isn't it? I'd at least expect a video of an exasperated Github user walking up to the '# days since the last GitHub incident' board, sliding out the '1' or '2' card, and replacing it with a '0'. I mean, that joke is as old as the universe (heck, in the brief period that I worked in an office, decades ago, I had a "# days since the last person asked a stupid question" sign to enact the exa…

I used to have a magic 8-ball that people could use when they wanted me to debug their code for them. I think it was broken, though; it kept saying "Outlook good". Must've been a Microsoft magic 8-ball.

Re: Days since last GitHub incident

#34

Post by latentsea »

bob1029 wrote: post #8
behnamoh wrote: post #5

[flagged]

GitHub was already done years ago. The ideal solution was in hand as of ~2020. Nearly every release since then has brought some kind of regression.

Hard disagree. GitHub Copilot is incredible. I can program pretty much entirely through my phone for large classes of problems now. Leveraged correctly it's amazing.

Re: Days since last GitHub incident

#35

Post by venturecruelty »

old_bayes wrote: post #17
ZeroConcerns wrote: post #11

This is a bit... low-effort, isn't it? I'd at least expect a video of an exasperated Github user walking up to the '# days since the last GitHub incident' board, sliding out the '1' or '2' card, and replacing it with a '0'. I mean, that joke is as old as the universe (heck, in the brief period that I worked in an office, decades ago, I had a "# days since the last person asked a stupid question" sign to enact the exa…

How can we add AI to this perfectly functional product?

Tie it to quarterly performance results!

Re: Days since last GitHub incident

#37

Post by verst »

bastardoperator wrote: post #27
llbbdd wrote: post #16

I've gotten accustomed lately to spending a lot of time in the Github Copilot / agent management page. In particular I've been having a lot of fun using agents to browse some of my decade-old throwaway projects; telling it to "setup playwright, write some tests, record screenshots/videos and commit them to the repo" works every time and it's a great way to browse memory lane without spending my own time getting some…

They do, it's called GHES. https://docs.github.com/en/enterprise-server@3.19/admin/over... "GitHub Enterprise Server is a self-hosted version of the GitHub platform"

That does not include the Copilot related APIs though.

Re: Days since last GitHub incident

#38

Post by ferguess_k »

I guess none of us really needs those 9s, and even two 9s are just good enough. I even doubt whether *SOME* of the banking transactions really really really need those 9s too -- like, I don't really mind if 1 out of 100 credit payment doesn't go through so I have to do it again -- it does happen once for a while and I just swiped it again.

Re: Days since last GitHub incident

#39

Post by AceJohnny2 »

bastardoperator wrote: post #27
llbbdd wrote: post #16

I've gotten accustomed lately to spending a lot of time in the Github Copilot / agent management page. In particular I've been having a lot of fun using agents to browse some of my decade-old throwaway projects; telling it to "setup playwright, write some tests, record screenshots/videos and commit them to the repo" works every time and it's a great way to browse memory lane without spending my own time getting some…

They do, it's called GHES. https://docs.github.com/en/enterprise-server@3.19/admin/over... "GitHub Enterprise Server is a self-hosted version of the GitHub platform"

you're not getting copilot on the self-hosted version, which is what the parent was focusing on.

Re: Days since last GitHub incident

#40

Post by Aurornis »

llbbdd wrote: post #16

I've gotten accustomed lately to spending a lot of time in the Github Copilot / agent management page. In particular I've been having a lot of fun using agents to browse some of my decade-old throwaway projects; telling it to "setup playwright, write some tests, record screenshots/videos and commit them to the repo" works every time and it's a great way to browse memory lane without spending my own time getting some…

None of the open weights models you can run locally will perform at the same level as the hosted frontier models. Some of them are becoming better, but the step-down in output quality is very noticeable for me.

> If Github sold a $5000 box I could plug into a corner in my house and just use that entire experience locally I'd seriously consider it. I'm guessing maybe I could get partway there by spending twice that on a Mac Pro but I have no idea what the software stack would look like today.

Right now, the only reasons to host LLMs locally are if you want to do it as a hobby or you are sensitive about data leaving your local network. If you only want a substitute for Copilot when GitHub is down, any of the hosted LLMs will work right away with no up front investment and lower overall cost. Most IDEs and text editors have built-in support for connecting to other hosted models or installing plugins for it.

> I know at least some people are managing local fleets of agents in some manner,

If your goal is to run fleets of agents in parallel, local LLM hosting is going to be a bottleneck. Familiarize yourself with some of the different tool options out their (Claude Code, Cline, even the new Mistral Vibe) and sign up for their cloud API. You can also check OpenRouter for some more options. The cloud hosted LLMs will absorb parallel requests without problem.

Post reply on HN