You must log in or # to comment.
I’ve used Teams in different places now and I’m coming to suspect the issue is less with Teams itself and more with upper management trying to cheap out on the infrastructure. A company I used to work for tried to cut down on their server expenses by minimizing the resources available to VMs. It meant Teams, made by the same company that makes an OS that gobbles both kinds of memory like it’s trying to fatten up for winter, worked as well as a vehicle with a leaky fuel line, which is to say poorly and with occasional fires and explosions. Another company I worked for had every part of Teams working fluidly. Phones, workstations, events and calendars, even the stupid AI BS, all ticking over nicely. The difference really seemed like it was in the infrastructure. With enough resources, it just worked.
For what it is, a chat app, Teams should run without any problems on machines from 2005
A chat app should basically run on a Casio wrist calculator with an antenna. A chat app designed by MS never will.
A-fucking-men
Oh no. Not teams 🤮🤮🤮
Never understood the hate. Teams is by far the most competent messaging platform out there. Way more intuitive that crap like Slack or Discord
Since I just had to deal with a Teams issue, I’m going to list some reasons I dislike it. Obviously, everyone’s mileage is different and something that bothers me may not bother others. However when people complain about Teams, it’s generally because of the following:
- It’s slow. I don’t care what MS says, Teams is really slow. It is slow to start, it’s slow to load content, and it’s slow to upload content to, and it’s slow to navigate around in. This doesn’t mean it’s painfully slow, but it’s slow enough that I think about it and that means it’s too slow. There is no excuse for performance like this in 2025 unless the excuse is you’re packing as much telemetry and data collection garbage as possible into the application.
- The integrations are really clunky (and also perform poorly). For example, if I upload a 30 second mp4 file it will go into Sharepoint and be served in MS Teams through MS Stream. Think about that for a second. A video file needed to be uploaded to Teams, shipped to Sharepoint for network storage, then read by MS Streams to feed back to Teams. Just render the fucking file in Teams. This isn’t hard. With the way they have it setup, the performance is terrible, the user experience is terrible, and it’s insulting that we’re being fed this bloated garbage. For context, I’m on a fiber connection and I still see buffering issues and slow video load times only in Teams so it clearly isn’t just something on my end.
- It randomly loses the ability to connect. Everything else works including other MS products but Teams won’t connect. Within the last 2 years, there have been at least half a dozen times where I turned on my computer in the morning and everything works except Teams. After a lot of searching for a solution, the fix was to delete two registry keys. Seriously, I have to go into the registry occasionally to delete two keys that are in no way tied to Teams based on their location in the registry before Teams will connect again when this happens. What the fuck is happening that Teams relies on two obscure registry keys that aren’t even located under any MS Teams nodes. Fucking awful.
- Did I mention performance? It is worth mentioning again because of how terrible it is. It is usable and gets the job done but people have no idea how much faster this could be if the bloat was removed. Slack isn’t exactly great from a performance perspective either but (at least in my experience) it’s much better than Teams.
- I keep getting prompts about copilot in Teams which is infuriating considering I’ve declined every time and it’s still enabled and still prompts me. I don’t need AI to summarize a one-sentence chat message FFS and I certainly don’t need help writing that sentence. Stop interrupting my flow to popup messages about features I’ve already told you I don’t want to use.
The majority of the above comes down to bad design leading to bad UX and performance. Why are they using a Streams instead of rendering the video in-app natively? Because it was cheaper to just tie into their Streams service. Why is it that only Teams randomly loses the ability to function? Because for some reason it relies on a legacy registry connection key because…reasons?
There isn’t a single bad thing about MS Teams, it’s a bunch of kinda bad things that together make the product terrible. We should demand better of our software products but all leverage has been given to the people who already control these things so we’re just screwed from getting actual good software made.
Also, screen sharing seems to take up most of your available RAM for some reason. When screen sharing, your chat window pops up to show everyone all your chats. The annoying ass top bar that needs to be moved every time and can’t remember its last location. Is teams a group chat, channel a group chat, or is group chat a group chat? Most add-ons are useless. Why does setting up a web hook notification with Teams require Power Automate? And why does it need a fixed schema? Just let me send any message I want!!
Ah I see. So the complaints aren’t really in the feature-set or design of the app, but rather the optimization.
That makes sense to me now. I was coming from the perspective of “I really like how information is organized and how collaboration works” not from a “does this app function well.”
I’ve never really had any performance issues, personally. Perhaps that’s bc I always used the Linux app back when I used teams and had a beefy PC. It had its own issues, but they were really with getting it to run in the first place. Once I could get it running, it always worked well for me.
Also, I was using it a couple years ago, pre-copilot, so maybe that’s added to the crappiness
you must be in management, because all that was bullshit.
