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.
/usr/bin/chromium --ozone-platform=wayland --enable-features=UseOzonePlatform,WaylandWindowDecorations,WebRTCPipeWireCapturer --user-data-dir=/home/myuser/.config/chromium-ilri --app=https://teams.microsoft.com
On my fairly ancient Core i7-8700 I can have a video call open in one screen and be editing in Resolve on another.
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.
An i5-14500 has a comparable memory bandwidth as an i9-14900k
https://www.intel.com/content/www/us/en/products/compare.htm...
MimeType=x-scheme-handler/foobar;
If not, I would write a shell wrapper and set it as the default browser; something to the effect of:
#!/usr/bin/bash
set -eu
for arg in "$@"; do
if [[ $arg == *whatever-url-teams-uses.com* ]]; then
exec gtk-launch teams "$@"
fi
done
exec gtk-launch firefox "$@"
And half of the time it crashes. Or the video/audio doesn't work.
The one thing that bothers me is it can't tell if I'm at my machine when I'm not actively using it. People keep thinging I've bugered off from my desk.
I've got two customers that both use Slack for everything except calls. One does calls in Meet and the other one in Teams. I asked to the Teams one and they told me that Teams works for everybody every time. Slack sometimes has problems with the video or audio setup. Too bad, because huddles are only one click away.
Granted I haven't tried O365 in about a year since it was so unusable in Firefox.
As far as teams goes, I use it in the same version chromium on the same OS on two different computers; one works fine most of the time (main issue is it sometimes switches the audio back to the first item listed by Linux, which is not my USB headset). The other computer is terrible. Somewhere between 4-48 hours it pops up a tiny (maybe 40px) banner at the top saying "you need to sign in again" meanwhile there are no notifications and any messages I send are silently queued with no obvious indication that they haven't been delivered. Before I figured this out, I was just randomly out of communication with my coworkers, with both sides thinking we were sending the other person messages that they were ignoring. Clicking the "sign in" button on the banner just seems to reload teams and doesn't even ask me to sign in.
Not surprised it properly works on Edge at all.
To me memory latency being whatever, 30% higher, ought not to explain the issue here, in part because that's a priori assuming all is memory-bandwidth-limited vs say network limited or CPU limited far as the bottleneck
What makes more sense to me is the software is "slow and clunky" that is maybe a global mutex, maybe poor multithreading sync making it effectively single threaded, with a sprinkling of particularly slow algorithms or syscalls that are realized as a frozen GUI, or as we call such cases, Microsoft standard