Live data from Hacker News

Ask HN: Why is Microsoft Teams still so bad?

news.ycombinator.com

401–410 of 814 posts

Re: Ask HN: Why is Microsoft Teams still so bad?

#401

On linux, Microsoft teams will change your system sound settings to match its preference. This includes Bluetooth headphones no longer being available to the system. Then, it decides the system settings are beneath it and will only use its own device settings. And it will decide now that your fancy Bluetooth headset is gone, there is also no need for that crappy internal microphone either, so enjoy not having any mic…

Install Microsoft Edge for Linux and use the web version through that.

Really, it's a great solution. I've done it for a while. I don't use edge for anything else but it runs teams.microsoft.com great

Re: Ask HN: Why is Microsoft Teams still so bad?

#402
Teams doesn't have to be good to succeed. It just has to exist. It's not even very important how good it is. Given it exists, IT will make everyone use it on Microsoft's behalf regardless of how bad it is.

Or another way to look at it is that the real customers for Teams are IT departments. It makes their lives easier because they don't have to do anything and it meets all the compliance requirements they are supposed to enforce.

Which in turn reflects that the real customers of IT are regulators and auditors. Nobody with decision making power actually cares whether any of the software in use in enterprises works well or not.

Re: Ask HN: Why is Microsoft Teams still so bad?

#404
post #392

My 2 cents of venting on this sorry excuse of software - Backtick formatting in a chat post only works after typing the closing backtick, deleting it, re-typing it - Text copied from a conversation is polluted with names and time stamps. "I really want this feature" said nobody ever - The mute/unmute button is hard to find, I don't think I've ever attended a Teams meeting without someone struggling with this. Teams s…

- images are deepfried when pasted into chats - can't copy an image from a chat and use it elsewhere; you have to find the download button, download it, go to your download folder, so people just screenshot the image in chat

cmd+tab only works on mac until you've received one notification, after that focus goes to an invisible window.

Re: Ask HN: Why is Microsoft Teams still so bad?

#405

Microsoft's entire business model is holding corporate IT hostage. All their apps suck, except maybe VS Code. There's no reason to choose the Microsoft stack over Google Workplace or Zoho except, well, inertia. And there's a lot of that...

i absolutely hate vscode but visual studio is incredible and one of the main reasons i use windows

Re: Ask HN: Why is Microsoft Teams still so bad?

#406

My 2 cents of venting on this sorry excuse of software - Backtick formatting in a chat post only works after typing the closing backtick, deleting it, re-typing it - Text copied from a conversation is polluted with names and time stamps. "I really want this feature" said nobody ever - The mute/unmute button is hard to find, I don't think I've ever attended a Teams meeting without someone struggling with this. Teams s…

- Last time I tried it didn't support screensharing on Wayland.

Re: Ask HN: Why is Microsoft Teams still so bad?

#407

It isn't because Microsoft lacks good programmers. My guess would be that someone believes they need to have every feature from slack, zoom, WebEx, meet etc, and also integrate tightly with every Skype/SharePoint/OneNote feature, and also run on at least four platforms. But they aren't willing to give people time to do this.

It's software that has never said no to a feature.

So you get a pile of conflicting goals.

Generally to resolve this you need to demand a high level of user competency. Think emacs; does everything, things are mutually exclusive, competency is required.

The teams approach though is to try to satisfy this without requiring any competency. It's probably not doable

Re: Ask HN: Why is Microsoft Teams still so bad?

#408
post #402

Teams doesn't have to be good to succeed. It just has to exist. It's not even very important how good it is. Given it exists, IT will make everyone use it on Microsoft's behalf regardless of how bad it is. Or another way to look at it is that the real customers for Teams are IT departments. It makes their lives easier because they don't have to do anything and it meets all the compliance requirements they are suppose…

My company is migrating to DaaS and there is a plethora of Teams issues. IT teams got what they deserve.

Re: Ask HN: Why is Microsoft Teams still so bad?

#410

Long ago Microsoft had MSN Messenger, which was one of the leading messaging apps. It worked well, and many 'normal' users were using it. Then Microsoft dissolved the team behind it and screwed up the product so bad with bloatware and ads that everyone moved to WhatsApp (except in the US where people went back to texting). Then Microsoft came out with Communicator, renamed it to Lync, which was a corporate messenger/…

Skype for Business (SfB) was not renamed Teams, the two products are completely unrelated, beyond Teams being a successor product to SfB.

Although there was a little bit of integration between SfB and Skype, (and between SfB and Teams as well) - so could communicate from one to the other.

Although Skype for Business Online was phased out in favour of Teams, the on-prem version still exists, probably for those customers that cannot/will not use Teams for regulatory/compliance reasons, and no end of life date has been announced for the on-prem version yet.

Post reply on HN