Live data from Hacker News

Microsoft is killing Skype

windowscentral.com

161–170 of 682 posts

Re: Microsoft is killing Skype

#161

Earlier quoted context omitted.

That all sounds like an issue with your particular setup more than with Skype. Just because that isn't how the Linux app works for most people at all.

Which thing? Relying on keychain to stay logged in, or bad startup performance, or the most recent minute-long freeze? GNOME/KDE users should have a keychain running, so it won’t affect them. It’ll only affect people who roll their own stack a bit more. I don’t object to it using the keychain if it’s available , but refusing to keep you logged in if it’s absent is bad. Nothing else acts like that.

I'm saying I think all the issues you are reporting, including the lag times and such, seem specific to your setup, maybe Sway specifically or Wayland. I don't use Gnome or KDE or have any keychain stuff installed, I run Alpine with Awesome, and haven't experienced the same issues you have.

Re: Microsoft is killing Skype

#162

Earlier quoted context omitted.

Personally I think their big, incomprehensibly stupid manoeuver was the Skype vs Skype for Business (Link) split. Had they merged them into a single client that could speak either protocol and share contact lists the story would have been very different. Why are megacorps so incomprehensibly clueless about this? Is the money pit so deep that they knock each other in while in-fighting for control on the edge of it?

Lync was completely unrelated software with a different tech stack that was just branded as Skype. https://en.wikipedia.org/wiki/Skype_for_Business

I know, that's my point - branding Lync (thanks for the correction, I forgot the spelling) damaged the Skype brand to no real benefit.

I know Teams is fairly pervasive, but that's on the usual Microsoft Enterprise stranglehold, certainly not on Teams' merits or riding the popularity of Skype pre Microsoft.

Re: Microsoft is killing Skype

#163
post #149
post #131

Earlier quoted context omitted.

This. In German the word for "video-calling" is "Skyping". Similar to MSN, the strength of the brand and goodwill that it has in some geographies is on-par with Google for search, or Coca Cola for coke. The fact that the software got consistently worse, year on year on year is hard to grasp for me. Microsoft made the right call to cannibalize and use teams. But how was Skype such a pain? Not being able to share scree…

In Germany, MS was very successful though to get organizations on Teams during the pandemic. Zoom is not a thing. Sure, it's nice to brand the verb, but when the product behind it is EOL, why bother.

That's because teams was offered for fee with m365 which most companies used anyway.

Having said that, Zoom is an absolutely terrible product. The backdoor they installed in Macs for example and then when it was brought to light refused to remove it until Apple was forced to blacklist the application. They're either incompetent or evil.

Re: Microsoft is killing Skype

#164

Earlier quoted context omitted.

Personally I think their big, incomprehensibly stupid manoeuver was the Skype vs Skype for Business (Link) split. Had they merged them into a single client that could speak either protocol and share contact lists the story would have been very different. Why are megacorps so incomprehensibly clueless about this? Is the money pit so deep that they knock each other in while in-fighting for control on the edge of it?

I think it was the other way around, they know about the issues with Skype and built something new, but they knew the power of the Skype brand so they slapped it onto their new product.

I think that must have been the logic. I just contend that it was a stupid approach! They damaged their consumer brand badly to give an imperceptible boost to the business product their customers were already locked into.

Re: Microsoft is killing Skype

#165
post #149
post #131

Earlier quoted context omitted.

This. In German the word for "video-calling" is "Skyping". Similar to MSN, the strength of the brand and goodwill that it has in some geographies is on-par with Google for search, or Coca Cola for coke. The fact that the software got consistently worse, year on year on year is hard to grasp for me. Microsoft made the right call to cannibalize and use teams. But how was Skype such a pain? Not being able to share scree…

In Germany, MS was very successful though to get organizations on Teams during the pandemic. Zoom is not a thing. Sure, it's nice to brand the verb, but when the product behind it is EOL, why bother.

Zoom is a thing in Germany.

Re: Microsoft is killing Skype

#168
Feels like Google never built anything successful themselves after the Search engine (maybe GMail), but rather bought stuff that became successful (e.g. Google Maps).

Conversely, Microsoft has built successful products (Windows, Office, ...), but it feels like whenever they buy something, they break it. Remember Nokia?

That's probably wrong, but it's how it feels to me now :).

Re: Microsoft is killing Skype

#169
post #41

Earlier quoted context omitted.

Skype for Business UX > MS Teams UX

But Skype for Business isn't even Skype. Wasn't it just a rebranding of MS Lync?

Yep. For the first few months after the rebranding, you could change a Windows registry setting to get the old Lync interface back.

Re: Microsoft is killing Skype

#170
post #21
post #4

It's amazing how much they dropped the ball during Covid. They already had everyone and everything in place! But the app is a buggy mess, far worse than Teams, and they just refused to do anything about it. I guess MS-internal politics? They had their own Teams and that was the preferred product?

If it was only Skype, Windows development has turned into a mess, it appears teams are filled with newly grads, without any background on Windows development, or Windows developer culture. That is why there are now Webview2 usage all over the place, and after 5 years WinUI 3.0 is still behind the WinForms, WPF and even MFC development experience, even though it should have been a plain port of UWP/WinUI 2.0 into stan…

I imagine internally they have a hard time staffing the Teams project. Like VSCode is a WebView2 project but it is miles ahead of Teams in quality. At least on the client side features seems far more complex too.

Teams used to use Angular 1 and I think they are still migrating out of it. Microsoft would need to pay me a lot of money to want to dive into that mess. I imagine there are a lot of devs who would love to be VSCode core developers though.

Post reply on HN