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

131–140 of 298 posts

Re: Another GitHub outage in the same day

#131

Post by tazjin »

bigbuppo wrote: post #94
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…

Not going to happen. This is terminal decline. Next step is to kill off free repos, and then they'll start ratcheting up the price to the point that they have one small dedicated engineering team supporting each customer they have. They will have exactly one customer. At some point they'll end up owned by Broadcom, OpenText, Rocket, or Progress.

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.

Re: Another GitHub outage in the same day

#132

Post by kimixa »

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?

It seems most of the complaints are about the reliability and infrastructure - which is very much often a direct result of lack of investment and development resources.

And then many UI changes people have been complaining about are related to things like copilot being forcibly integrated - which is very much in the "Microsoft expect to gain a profit by encouraging it's use" camp.

It's pretty rare companies make a UI because they want a bad UI, it's normally a second order thing from other priorities - such as promoting other services or encouraging more ad impressions or similar.

Re: Another GitHub outage in the same day

#133

Post by TacticalCoder »

heliumtera wrote: post #98

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...

> 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.

Re: Another GitHub outage in the same day

#134

Post by dizhn »

1f60c wrote: post #19
kevmo314 wrote: post #12

I wonder if GitHub is feeling the crush of fully automated development workflows? Must be a crazy number of commits now to personal repos that will never convert to paid orgs.

IME this all started after MSFT acquired GitHub but well before vibe coding took the world by storm. ETA: Tangentially, private repos became free under Microsoft ownership in 2019. If they hadn't done that, they could've extracted $4 per month from every vibe coder forever(!)

Is someone who is not really using github's free service losing something important?

Re: Another GitHub outage in the same day

#135

Post by matthewisabel »

sobjornstad wrote: post #8
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…

I second this. GitHub used to be a fantastic product. Now it barely even works. Even basic functionality like the timeline updating when I push commits is unreliable. The other day I opened a PR diff (not even a particularly large one) and it took fully 15 seconds after the page visually finished loading -- on a $2,000 dev machine -- before any UI elements became clickable. This happened repeatedly. It is fairly stun…

Hey from the GitHub team. Outages like this are incredibly painful and we'll share a post-mortem once our investigation is complete.

It stings to have this happen as we're putting a lot of effort specifically into the core product, growing teams like Actions and increasing performance-focused initiatives on key areas like pull requests where we're already making solid progress[1]. Would love if you would reach out to me in DM around the perf issues you mentioned with diffs.

There's a lot of architecture, scaling, and performance work that we're prioritizing as we work to meet the growing code demand.

We're still investigating today's outage and we'll share a write up on our status page, and in our February Availability Report, with details on root cause and steps we're taking to mitigate moving forward.

[1] https://x.com/matthewisabel/status/2019811220598280410

Re: Another GitHub outage in the same day

#136

Post by dev_l1x_be »

catigula wrote: post #116
dev_l1x_be wrote: post #110

Earlier quoted context omitted.

So React rewrite did not help after all? Imagine, one of the largest software tool companies on Earth cannot reliably REbuild something in React. I lost count of the inconsistency issues React introduced. https://news.ycombinator.com/item?id=33576722

React isn't causing these issues.

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

Re: Another GitHub outage in the same day

#137

Post by bigbuppo »

tazjin wrote: post #131
bigbuppo wrote: post #94

Earlier quoted context omitted.

Not going to happen. This is terminal decline. Next step is to kill off free repos, and then they'll start ratcheting up the price to the point that they have one small dedicated engineering team supporting each customer they have. They will have exactly one customer. At some point they'll end up owned by Broadcom, OpenText, Rocket, or Progress.

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?

Re: Another GitHub outage in the same day

#138

Post by stackskipton »

noodlesUK wrote: post #61
zero_shift wrote: post #42

Earlier quoted context omitted.

So I work for a devtools vendor (Snyk) and 6 months ago I signed into Azure DevOps for the first time in my life I couldn't believe it. I actually thought the product was broken. Just from a visual perspective it looked like a student project. And then I got to _using_ the damn thing

It's also completely unloved. Even MSFT Azure's own documentation regularly treats it as a second class citizen to GitHub. I have no idea why they don't just deprecate the service and officially feature freeze it. Honestly that's the case with a lot of Azure services though.

Someone mentioned the boards but Pipelines/Actions are not 100% compliant.

My company uses Azure DevOps for a few things and any attempt to convert to GitHub was quickly abandoned after we spent 3 hours trying to get some Action working.

However, all usability quarks aside, I actually prefer these days since Microsoft doesn't really touch it and it just sits in corner doing what I need.

Re: Another GitHub outage in the same day

#139

Post by Etheryte »

matthewisabel wrote: post #135
sobjornstad wrote: post #8

Earlier quoted context omitted.

I second this. GitHub used to be a fantastic product. Now it barely even works. Even basic functionality like the timeline updating when I push commits is unreliable. The other day I opened a PR diff (not even a particularly large one) and it took fully 15 seconds after the page visually finished loading -- on a $2,000 dev machine -- before any UI elements became clickable. This happened repeatedly. It is fairly stun…

Hey from the GitHub team. Outages like this are incredibly painful and we'll share a post-mortem once our investigation is complete. It stings to have this happen as we're putting a lot of effort specifically into the core product, growing teams like Actions and increasing performance-focused initiatives on key areas like pull requests where we're already making solid progress[1]. Would love if you would reach out to…

Literally everyone who has used Github to look at a pull request in say the last year has experienced the ridiculous performance issues. It's a constant laughing point on HN at this point. There is no way you don't know this. Inviting to take this to a private channel, along with the rest of your comment really, is simply standard corporate PR.

Re: Another GitHub outage in the same day

#140

Post by gerdesj »

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…

The ultimate irony is that Linus Thorvalds designed git with the Linux kernel codebase in mind to work without any form of infrastructure centralisation. No repo trumps any other.

Surely some of your crazy kids can rummage up a CI pipeline on their laptop? 8)

Anyway, I only use GH as something to sync interesting stuff from, so it doesn't get lost.

Post reply on HN