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
The web-based one works perfectly on Linux. If anything it's better than the native Windows app.

Office 365 actually works better in Firefox in Linux than any other browser in Windows. It's like they've kind of given up on the whole OS thing, and have just decided to go with Linux.

>>Errone+2ex
If by perfect you mean that you can’t have two chats open next to each other and toggling between chats is slow as molasses then yes.

>>Too+mgx
Are you running it on a particularly potatoey PC?

On my fairly ancient Core i7-8700 I can have a video call open in one screen and be editing in Resolve on another.

>>Errone+Omx
There's something weird going on honestly.

On an i9-14900K, arguably one of the fastest CPUs in the previous few years (and excusing their design defect that causes them to die); Teams is significantly slower than on the Quallcom Snapdragon X-Elite, or my Macbook.

It seems to perform the same as it would on an i9 platform as it does on i5 laptop's of the same generation (in terms of input latency and drawing to the screen etc;)

I know it's apples/oranges, that ARM CPUs are substantially different than x86 ones, but the fact that it seems to be the same on significantly lower clocked (and lower consumptive) chips indicate to me that something very bizarre is happening when it comes to Teams.

ARM chips seem to be significantly better for electron applications, but something unique exists within Teams here.

>>dijit+9nx
No idea, but I have found that edge can be more conservative in its use of GPU acceleration than Chrome. Maybe that is the case in the webview Teams uses.