[hbn]

VS Code's selling point is that it's a middle-ground between (relatively) lightweight performance of a text editor, and power of an IDE. People are keeping an eye on performance, and they'll stop using it if it just becomes a bloated, master-of-none IDE.

Teams' bread and butter is being "good enough" for enterprise. And they're also locked into a lot of bad early decisions they made since they don't want to break compatibility for huge, paying customers of theirs. I feel like they have to be incredibly careful making changes to not step on toes in that regard, making development a slow-moving behemoth.

[CamperBob2]

What do people not like about Teams? I just started using it with a contract customer and it seems fine. Does what it says on the proverbial tin.

[PeterisP]

Teams, unlike pretty much every competing solution, is horrible when working with multiple different identities. If you have an account with an employer, a university and multiple clients, switching them is a pain (compare and contrast, for example, Slack). If you want to get a meeting in your Teams organization and invite a few people who are currently logged in their own organization, it is a pain to do so, and may involve them signing off of all kinds of other key MS tools they need to use during the meeting. If you want to use your phone to be in 'chats' of three different Teams organizations (e.g. three different consulting customers) at the same time, without switching between them but just monitoring all of them at the same time, I'm not sure if it can be reasonably done, and that IMHO is a relatively simple need and one which everyone else somehow manages to do better.

[taormina]

I have to use Google Hangouts or Meet or whatever it’s called now, Zoom, Teams and Slack Huddles. Teams consistently screws up audio, video or both! Then we end up back in Slack.

[rirze]

For the last couple of months, I occasionally don't get notifications if the app is not focused. And it's not just me, several team members are experiencing the same issue. Imagine-- a messaging app that doesn't deliver notifications when running in the background.

[macintux]

No notifications (which honestly I’m fairly happy about, my team’s important communications happen in Slack), the frequent rejection of mouse clicks (literally took me 30+ clicks to share my screen today), the bizarre window behavior as you switch monitors, windows vanishing as you switch apps… it’s just a nightmare.

[JohnFen]

The UI is pretty awful in a bunch of ways. The performance is hit-or-miss at best. It's a resource hog. These are my top-line irritations with Teams. If I weren't forced to use it by my employer, I'd happily never touch it again.

[__s]

The UI isn't smooth. Notifications will appear & then the message won't show up for a few seconds. Scrolling back through history can start flickering all over the place. It takes up a lot of memory

[98codes]

You running 64GB or 128Gb of ram?

[CamperBob2]

Admittedly I'm using a fast machine they configured and issued to me (i7-12850HX with 64 GB), and with a decent (50 Mb/10 Mb) broadband connection. Haven't had to do much with Teams yet, but it hasn't actively pissed me off.

[dw-im-here]

I have 128Gb RAM, it's not enough to make ms teams remotely close to acceptable because the UX is still like a parodical mashup of every bad idea microsoft has ever had.