I really cannot express in words adequately how awful teams is for me, on MacOS 10.14, on Arch Linux, or in the [chromium only!] browser. It's a memory and CPU

I really cannot express in words adequately how awful teams is for me, on MacOS 10.14, on Arch Linux, or in the [chromium only!] browser. It's a memory and CPU hog, the classic example of a terrible electron app, has appalling videoconferencing skills, and is thrust down my throat from those Upon High. If I were MS, I'd be very worried about another anti-trust suit coming shortly. It's objectively worse than all the competition, the UI is appalling, and there's no support. It crashes randomly. Different versions crash for different reasons. I've seen debug logs after crashes -- which, incidentally, are either segfaults or graceful quits -- indicating that an "ERROR_SUCCESS" is returned after an AD authentication and the whole thing just dies. The current bug is that I can't make calls using the app, only the webapp in Chrome -- it literally just says "There is a connection issue", but doesn't elucidate further what it is. I can reproduce this 100% of the time, but I can't directly raise a bug report (beyond, say, this [0]) and even have a nice video of the steps to reproduce on my machine -- open the application, and try to call someone. Clearly, something is "wrong" with my AD profile in a big way, and it's in MS's interests to reach out, talk with my employer, and find out what's going on. Naturally, this hasn't happened, and I use Zoom as a marginally less frustrating alternative. [0] https://answers.microsoft.com/en-us/msteams/forum/msteams_tfb-msteams_tfmac/i-cannot-join-calls-on-teams-for-macos/0daae1e9-63bd-4a0d-ad4b-04c7cfb0ac8f?tm=1599919430600 https://answers.microsoft.com/en-us/msteams/forum/msteams_tf...