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.
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.
It's also a CPU hog. Why can I watch a 4K video in VLC for hours, but throwing up a couple of 200x100 windows in Teams kills the CPU? I guess Teams is written by interns.
Re:GitHub incident: 2022/03/24
by klhutchins on Thursday March 24, 2022 @12:12PM
(#30791888)
I just think about why would they force video conferencing into SharePoint?
Re:GitHub incident: 2022/03/24
by anaccountexists on Thursday March 24, 2022 @12:14PM
(#30791914)
Teams is built on top of Skype for Business, SfB is one of the main backends for them.
Re:GitHub incident: 2022/03/24
by iratewizard on Thursday March 24, 2022 @11:48AM
(#30791548)
They got patent trolled and flinched. They removed the things that made Skype best in class and turned it into just another low quality corporate messenger.
Was it really due to that lawsuit? IIRC the main issue with P2P was that you could discover anyone's IP address by knowing their Skype username. I recall that people used this to DoS people in multiplayer video games - they looked up accounts with roughly the same name as the in-game one and proceeded to drop their connection. It was especially common in League of Legends.
Re:GitHub incident: 2022/03/24
by throwaway89645 on Thursday March 24, 2022 @07:49PM
(#30797024)
Yep - It was bad enough that it was common practice for people to proxy their skypes through a third party.
(It was pretty nice that Skype let you do that really easily though)
Re:GitHub incident: 2022/03/24
by tonyedgecombe on Thursday March 24, 2022 @12:19PM
(#30791997)
€5.4bn for Nokia and that didn't work out for them either.
Anecdotal: It's still the primary communications thing in my company and probably our customers (telecoms / networks, probably quite archaic).
> At this point, Gitea, Gitlab and others (self hosted or otherwise) are beginning to gain traction as a more reliable and performant alternative.
Well there you go. The lesson is to not go 'all in' or 'centralize everything' on GitHub, which is what everyone was doing and why it has now become increasingly unreliable as I predicted, years ago in the long run. [0]
Perhaps it is time to self-host then?
Did you see the following post? I can't prove the underlying issue caused this issue but I'd wager it's likely. And I'd wager they ARE prioritizing this. https://github.blog/2022-03-23-an-update-on-recent-service-d...
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.
Youre facing the very real possibility of spending nearly eight billion dollars to capture the developer mindshare of the internet, only to lose it in just four years.