zlacker

>>basemi+(OP)
Alternative solution: Flee any company that uses Microsoft Teams.

>>neilv+ryw
The last couple of places I worked at used Teams, as did a number of the clients. We never found anything much better for the video calling aspect, and my understanding is that Teams comes for free with all the other Microsoft Shit - so you may as well.

I didn't find the chats/discussion UI at all clear initially, but once I'd had it explained to me, I could see what was going on.

(I do remember it taking a long time to load, and apparently using a surprising amount of memory once it was finally done, but aside from providing reliable fodder for water cooler conversations with other 40+ year old colleagues this never actually seemed to cause a problem in practice. At my last Teams-using job I would restart my PC no more than once or twice a week, something I could let happen in parallel with making the cup of tea that I'd always be making at some point anyway. And it had 64 GB RAM, which isn't even a lot by today's standards, but still Teams didn't actually fill all of it.)

>>tom_+0Bw
Zoom, Slack and Google Meet all work as well or better than Teams for it's primary purpose: video calls. Teams freezes up, consume ALL your resources, going from one call to another and it just stops working. The only thing I've used that's worse is Chime.

>> I didn't find the chats/discussion UI at all clear initially, but once I'd had it explained to me, I could see what was going on.

This is an example of how bad it is: you had to have the chat UX explained to you. Combined with MS cramming as much crap into teams as possible and trying to tie you to their other products with integrations that barely or rarely work - and the AI features are terrible (and yet another MS AI offering called Copilot?). It really is that bad and I'm glad I no longer have to use it.

>>skeete+YBw
I don't see this behaviour at all, and I live in Teams on Windows, web and Android. It has improved over time.