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

Another GitHub outage in the same day

githubstatus.com

Post reply on HN
Print view View original

151–160 of 298 posts

Re: Another GitHub outage in the same day

#151

Post by danudey »

dev_l1x_be wrote: post #136
catigula wrote: post #116

Earlier quoted context omitted.

React isn't causing these issues.

Good to know. So it only causes the UI inconsistency bugs.

The new design/architecture allows them to do great stuff in the name of efficiency; for example, when browsing through some parts of the UI, it's now much more capable of just updating the part of the page that's changed, rather than having to reload the entire thing. This is a significantly better approach for a lot of things.

I understand that the 'updating the part of the page that's changed' functionality is now dramatically slower, more unresponsive, and less reliable than the 'reload the entire thing' approach was, and it feels like browsing the site via Citrix over dial-up half the time, but look, sacrifices have to be made in the name of making things better even if the sacrifice is that things get worse instead.

Re: Another GitHub outage in the same day

#152

Post by monkaiju »

chilipepperhott wrote: post #79
bstsb wrote: post #27

my four-core VPS running a Git server has higher uptime than GitHub at this point (although admittedly less load and redundancy)

Does redundancy even matter if the end result is still poorer uptime?

Exactly! Also operating "at scale" is only impressive if you can do it with comparable speed and uptime, it doesn't mean much if every page takes seconds to load and it falls over multiple times a day lol

Re: Another GitHub outage in the same day

#153

Post by dmix »

neuropacabra wrote: post #126
9cb14c1ec0 wrote: post #103

Earlier quoted context omitted.

Yes, millions of people running code agents around the clock, where every tiny change generates a commit, a branch, a PR, and a CI run.

I simply do not believe that all of these people can and want to setup a CI. Some maybe, but even after the agent will recommend it only a fraction of people would actually do it. Why would they?

Github CI is extremely easy to set up and agents can configure it from the local codebase.

Re: Another GitHub outage in the same day

#154

Post by philipallstar »

noodlesUK wrote: post #3

Can someone in GitHub senior leadership please start paying attention and reprioritise towards actually delivering a product that's at least relatively reliable? I moved my company over to GH enterprise last year (from AzDO) and I'm considering moving us away to another vendor altogether as a result of the constant partial outages. Things that used to "just work" now are slow in the UI, and GH actions fail to schedul…

Honestly, Gitlab is pretty decent.

Re: Another GitHub outage in the same day

#155

Post by danudey »

tibbar wrote: post #40
kimixa wrote: post #18

Earlier quoted context omitted.

We loved Github as a product when it needed to return or profit beyond "getting more users". I feel this is just the natural trajectory for any VC-funded "service" that isn't actually profitable at the time you adopt it. Of course it's going to change for the worse to become profitable.

GitHub isn't VC funded at the moment, though. It's owned by Microsoft. Not that this necessarily changes your point.

> Of course it's going to change for the worse

> It's owned by Microsoft.

I see no contradictions here.

Re: Another GitHub outage in the same day

#156

Post by dec0dedab0de »

monkaiju wrote: post #144
dec0dedab0de wrote: post #111

I still say that mixing CI/CD with code/version control hosting is a mistake. At it's absolute best, everything just works silently, and you now have vendor lock-in with whichever proprietary system you chose. Switching git hosting providers should be as easy as changing your remotes and pushing. Though now a days that requires finding solutions for the MR/PR process, and the wiki, and all the extra things your team…

I mean, not necessarily proprietary right? There are OSS solutions like forgejo that make it pretty simple, at least as simple as running a git system and a standalone CI system

i mean that is certainly better, but I still don’t like having them coupled. Webhooks were a great idea, and everyone seems to have forgotten about them.

Re: Another GitHub outage in the same day

#157

Post by danudey »

notpushkin wrote: post #85
kimixa wrote: post #18

Earlier quoted context omitted.

We loved Github as a product when it needed to return or profit beyond "getting more users". I feel this is just the natural trajectory for any VC-funded "service" that isn't actually profitable at the time you adopt it. Of course it's going to change for the worse to become profitable.

I don’t get it. Why making the UI shittier would possibly lead to more profit?

Moving to client-side rendering via React means less server load spent generating boilerplate HTML over and over again.

If you have a captive audience, you can get away with making the product shittier because it's so difficult for anyone to move away from it - both from an engineering standpoint and from network effects.

Re: Another GitHub outage in the same day

#158

Post by danudey »

bigbuppo wrote: post #137
tazjin wrote: post #131

Earlier quoted context omitted.

Killing off free repos is not going to happen. That would be a suicide move on the level of the Digg redesign, or Tumblr's porn ban. It kind of would be good for everyone if they did do it though. Need to get rid of this monopoly, and maybe people will discover that there are alternatives with actually good workflows out there.

They are owned by Microsoft. When has Microsoft ever had a good idea?

Buying Github seems like a good idea? But fucking it up wasn't, so maybe it comes out even.

Re: Another GitHub outage in the same day

#159

Post by 0xy »

nfg wrote: post #121
kasey_junk wrote: post #5

Earlier quoted context omitted.

“ I enjoy GH copilot as much as the next person” So not at all?

Really? I’d be interested to hear more. Disclaimer: I work in Microsoft (albeit in a quite disconnected part of it, nothing to do with GitHub or Copilot).

Not even Microsoft employees like Copilot. Maybe start why not even your coworkers can use your own slop.

https://www.theverge.com/tech/865689/microsoft-claude-code-a...

Re: Another GitHub outage in the same day

#160

Post by bsimpson »

h4kunamata wrote: post #143

GitLab is the solution, if you aren't on it already. I worked for one of Australia largest airline company, monthly meeting with Github team resumed in one word: AI There is zero focus into the actual platform as we knew it, it is all AI, Copilot, more AI and more Copilot. If you are expecting things to get better, I have bad news for you. Copilot is not being adopted by companies as they hoped, they are using Claude…

Do they have their own model? I thought Copilot was a frontend for Clause et. al..
Post reply on HN