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

GitHub incident: 2022/03/24

githubstatus.com

Post reply on HN
Print view View original

21–30 of 103 posts

Re: GitHub incident: 2022/03/24

#21

Post by queuebert »

awill wrote: post #12
nimbius wrote: post #10

https://www.githubstatus.com/ at the time of posting, webhooks and actions are still struggling :( there have now been 23 incident outages in 90 days. if anyone from Microsoft is reading this, you need to start considering this degradation as the companies highest priority. At this point, Gitea, Gitlab and others (self hosted or otherwise) are beginning to gain traction as a more reliable and performant alternative.…

Isn't that basically what happened to Skype? Microsoft paid $8.5B for Skype when it was on top of the world, and now I don't know a single person who uses it.

When my organization uses a Microsoft video conferencing product, we use Teams, not "Skype for Business". I have no idea why, as I don't schedule the meetings, but I can say that I can't imagine something sucking worse than Teams.

Re: GitHub incident: 2022/03/24

#22

Post by semiquaver »

tastywheat wrote: post #17

Quoted post unavailable.

GitHub didn’t impose any requirement to use ‘main’ as the default branch. We merely changed the default for new repos unless the user or org has configured otherwise. Nothing about that (optional) change would have required any company to change any of what you listed.

Re: GitHub incident: 2022/03/24

#23

Post by shafyy »

queuebert wrote: post #21
awill wrote: post #12

Earlier quoted context omitted.

Isn't that basically what happened to Skype? Microsoft paid $8.5B for Skype when it was on top of the world, and now I don't know a single person who uses it.

When my organization uses a Microsoft video conferencing product, we use Teams, not "Skype for Business". I have no idea why, as I don't schedule the meetings, but I can say that I can't imagine something sucking worse than Teams.

Teams is the worst. I constantly miss messages, the video calling feature randomly freezes videos of participants, and sometimes my audio doesn't work for no apparent reason. Their Wiki feature sucks, too.

Re: GitHub incident: 2022/03/24

#24

Post by rsstack »

queuebert wrote: post #21
awill wrote: post #12

Earlier quoted context omitted.

Isn't that basically what happened to Skype? Microsoft paid $8.5B for Skype when it was on top of the world, and now I don't know a single person who uses it.

When my organization uses a Microsoft video conferencing product, we use Teams, not "Skype for Business". I have no idea why, as I don't schedule the meetings, but I can say that I can't imagine something sucking worse than Teams.

"Skype for Business" sucks more than Teams. But it's true: it's hard to imagine something like "Skype for Business". I had to use it for a few months when working with a business unit in a different country that were all forced to use it. We were all happy when their business unit's IT department agreed to move them from Skype to Teams.

Re: GitHub incident: 2022/03/24

#26

Post by Cthulhu_ »

awill wrote: post #12
nimbius wrote: post #10

https://www.githubstatus.com/ at the time of posting, webhooks and actions are still struggling :( there have now been 23 incident outages in 90 days. if anyone from Microsoft is reading this, you need to start considering this degradation as the companies highest priority. At this point, Gitea, Gitlab and others (self hosted or otherwise) are beginning to gain traction as a more reliable and performant alternative.…

Isn't that basically what happened to Skype? Microsoft paid $8.5B for Skype when it was on top of the world, and now I don't know a single person who uses it.

Anecdotal: It's still the primary communications thing in my company and probably our customers (telecoms / networks, probably quite archaic).

Re: GitHub incident: 2022/03/24

#27

Post by Cthulhu_ »

tastywheat wrote: post #17

Quoted post unavailable.

Git (hub) doesn't care what you name your main branch, that was all you / your org; see https://docs.github.com/en/repositories/configuring-branches... on how to change the default branch in your Github-hosted repository. The new default for new repos is 'main' these days but it's arbitrary (also consider how many repos have 'development' as their default branch)
Post reply on HN