[tedggh]

What’s so bad about Teams that makes it so hated? I used it lately and often to work with a customer and I don’t find anything terrible about it, other than some minor usability annoyances like phantom chat notifications once in a while. But overall it does what it’s supposed to do, get on a video call, share your screen and share files over channels. The transcript feature seems to work well too. I’m not amazed by it, but I don’t see anything to hate either. I guess it is one of those tools I don’t have a strong opinion about.

[dijit]

"I don't have an issue with it" tells me you've never used anything else. Have you tried Slack? Zulip? Mattermost? Fucking... IRC from 1988?

Teams isn't just mediocre, it's aggressively hostile to basic usability. The camera bar sits at the top of the window, directly blocking where you're supposed to position your camera for eye contact. Chat organisation is broken: you get duplicate groups because the order people were added matters somehow. Notifications phantom in and out. Reactions are buried in an activity feed. Search is useless. You can't reliably paste text without major formatting issues. The mobile app logs you out randomly and doesn’t tell you unless you manually check it. Desktop notifications don't sync with read state. Files uploaded to chat don't appear in the Files tab. The "new Teams" broke half the features that worked in classic Teams. Presence status is a coin flip. Audio settings reset themselves between calls. Screen sharing has a 50/50 chance of sharing the wrong window. The difference between a chat and a channel is arbitrary and confusing. You can't edit messages older than a few hours. Threading is bolted on and barely works.

Performance is inexcusable. Multiple gigabytes of RAM to display text messages and lag constantly on modern hardware. How do you make a chat application lag? It's rendering text, not computing fluid dynamics. Opening the application takes 30 seconds on an SSD. Switching between chats stutters. Typing has input delay.

The real problem isn't that Teams is terrible. It's that "it technically functions" has become an acceptable standard. When you've never experienced better, "it works" seems fine. But Teams is what happens when a monopoly position means you don't have to care about quality. Microsoft has unlimited resources and still ships this.

Even Skype for Business was more stable, and in Skype for Business you couldn't reliably select text. That's how low the bar is.

[mystifyingpoi]

> and lag constantly on modern hardware

This. Opening a chat for the first time in the morning consistently takes 5-10 seconds. Opening subsequent ones takes 2-3 seconds. That is, if they contain plain text. If not, UI keps reflowing and jumping while thumbnails and silly gifs are loaded async, so you cannot even reliably click.

[9dev]

Out of all the things you listed (and I'd have a couple more), copy-paste is really what drives me insane, because it's completely cursed!

Sometimes, text copied from teams includes `[Sender Name, 2026-01-03, 21:51]` as a prefix—other times not. Sometimes you paste formatted text and it ends up pasted as formatted but inconsistent HTML, including (of course) text color of all things, rendering it black even with the dark theme, and thus unreadable. Other times you copy code, and there's two blank lines between each line when you paste elsewhere. It makes you cry, really.

[tedggh]

I have used at least Skype, Meet/Chat, Slack, Teams and Discord, plus some other niche apps I can’t remember. In Discord, I like the ability to share user screens concurrently and the way you can just jump on a channel and have an impromptu meeting without much ceremony. But I have seen only one case of Discord in a corporate environment. My use cases are simple, video calls, screen sharing, file sharing and chat with mentions and code snippets, once in a while a survey to pick a place for lunch. I have been using Teams daily since last October. No issues. If it was consistently bad, it would have been replaced already. People I work with value their time. Also last week I was in a 2K+ people presentation with Q&A. I haven’t experienced most of the issues you mentioned, and don’t have the use case for some, like search or mobile. I use my email as my source of truth for communications, if it’s not in my inbox it didn’t happen. We are very diligent in keeping meeting minutes and transcripts which are shared my email at the end of the each call.

[zelphirkalt]

Let's not forget how stupid the client on GNU/Linux was regarding audio devices. Every other app I had installed, that has anything to do with microphone (OBS, Audacity, Discord, Discord in Browser, Signal, ...) recognized my mic, which was connected via jack. Not MS Te-eams!!! Tada! Had to buy another headset with USB plug for Teams to get it.

[mrweasel]

> Typing has input delay.

Everything in Windows has input delay, ever since at Windows XP, it makes it infuriating to use.

[cmoski]

Notifying you about messages you've already seen. You have to change chats and to back for it to dismiss it. Kills me.

Likes to open new windows if you click a notification.

It is slow.

The search is not good at showing multiple results from the one chat. Why does it search all the other chats anyway...

Switching accounts constantly is a pain in the arse - I unfortunately have to use four accounts and one sub-account (member of some other org's team or something).

[Agingcoder]

It has a very large number of bugs.

My favourite one ( still happens ) is having to mute then unmute at the beginning of the conversation otherwise nobody can hear me. It was so common, with people fiddling with their headset, calling again etc that I eventually asked everyone exhibiting audio issues to start with this

Another interesting one is that if you’re not connected properly , you send messages , but never get notified that they never left, and are never notified that you’re not connected.

It’s also a resource hog and will eat your machine for breakfast.

The list goes on and on, it’s very surprising.

[rootusrootus]

I don't love it, but I don't have many of the problems other people seem to have. And I've used everything from IRC in the 80s to Slack more recently. The only thing I can think of is that I don't run it on Windows, but rather a fairly new MacBook Pro M4. Maybe in this case it actually runs better on Mac, which is kind of ironic.

[wolvoleo]

It's a resource hog, crashes, it's constantly littering files all over SharePoint which becomes even more than a garbage bin than it already is.

And the UI is terrible, huge balloons around everything. I want density but even at the densest setting it sucks.

Oh and it also fails to update online status. Often I click on a colleague who seems green and only then it updates and it turns out they've been away for 3 hours. Grrr

[isk517]

Another one for the pile. You can choose to open office documents in Teams directly, the browser, or in the native desktop app, but you can only set it to open by default in either Teams or browser. Why?

[CamperBob2]

Teams feels as though it were vibe-coded, but dates back well before there was such a thing. It works, basically, but isn't something I'd feel good about shipping myself.

[perching_aix]

Wrote up a few of my gripes on here a few months ago: https://news.ycombinator.com/item?id=45933952