zlacker

>>basemi+(OP)
The official client is absolutely terrible. But, I've found a much better solution: I tell all my customers Microsoft Teams doesn't work for us and they'll have to pick something else.

Kudos for at least trying to address this, MS should hang their head in shame, this is not the hardest problem to solve these days. If we could do it in 1995 they should be able to do it 30 years later.

>>jacque+G6x
Teams doesn't work much better on Mac. It's easily the worst program I have to use.

>>Gigach+eax
I thought it was due to Mac not being their native platform, and then I tried Windows, and it's as crappy there as it is on a Mac.

Microsoft does not do web-based and distributed end-user software well. All sorts of organizational dysfunction leaks in the implementation (it's obvious one team was in charge of "grouping", and another is in charge of "channels", and no connection to any of the Teams calls for a group which and god-forbid Outlook). They are in dire need of some "inverse Conway maneuvering", but with a behemoth like MS, it's probably a mindset shift that's impossible to get through for any of the projects they are building today.

If at least they were still focused on doing good desktop software, I'd give them a pass, but they are increasingly introducing the same problems in the desktop software they build too.

However, I wonder even more what's wrong with my organization to keep using such subpar tools for years now :(