xD.
-
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
-
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.
-
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!!
-
Never understood the hate. Teams is by far the most competent messaging platform out there. Way more intuitive that crap like Slack or Discord
Well if you compare it with shit you set the bar unnececarily low.
If you actually can and want to look for something better that feels teams-like enough and actually doesnt suck?
Give Mattermost a shot.
Its FOSS and comes with a Paid Option - for Corps of a Size where you want active support.Comp I work for uses it and I fucking love it.
-
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.
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
-
Never understood the hate. Teams is by far the most competent messaging platform out there. Way more intuitive that crap like Slack or Discord
Had you said Teams is the most comprehensive collaboration platform I would have been right there with you.
But Teams is really just a Sharepoint front-end with tacked on voice and text chat. Itās not a messaging platform.
-
Never understood the hate. Teams is by far the most competent messaging platform out there. Way more intuitive that crap like Slack or Discord
Because itās buggy trash software with a terrible UI
-
Never understood the hate. Teams is by far the most competent messaging platform out there. Way more intuitive that crap like Slack or Discord
you must be in management, because all that was bullshit.
-
Never understood the hate. Teams is by far the most competent messaging platform out there. Way more intuitive that crap like Slack or Discord
My biggest problem with Teams is that it doesnāt deliver messages when it thinks the computer isnāt active. Got Teams running on Computer A while youāre working on Computer B? Donāt expect to see anything from anyone, not even if you frequently glance over at your other monitor.
I got a mouse wiggler just so that I could get messages.
The most fundamental feature of a messaging platform is messaging. If it canāt do that properly, which for some reason Teams canāt or wonāt, then it deserves all the hate it gets.
-
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.
What about it using at least 1 GB of RAM, and growing continuously while youāre using it until the OOM killer has gotten enough and kills it?
