zlacker

> It works fine 19 times out of 20 at least.

But for something you use 3-5x a day, that is a noticeable problem every few days. Why it has such an awful reputation.

>>MattGa+(OP)
So so all of the hate is just due to some dropped calls? Realistically it isn't even that bad (likely more like 2% failure rate). For me, I use Teams but it isn't like I am in the application all day. If it were 10X better I wouldn't care very much - like MS word vs Google docs or whatever. I care a lot about text editors on the other hand.

>>osigur+B6
The hate comes, deservedly I might add, from a lot more than just dropped calls. Terrible UI. Horrendous performance. Bloated apps. Confusing UX. Completely broken integration with the desktop/browser.

Teams is an absolute mess.

>>okayju+tt
>> Horrendous performance

When I click on something in Teams it shows up in (I'd say) < 300ms most times. I'm sure it could be much faster if done better. However, is that what you mean by "horrendous" or are you seeing 30s freezes or something like that?

>>osigur+sH
Using Teams on Safari on a maxed out M2 Pro machine proves to be a ridiculously slow affair. Moving between sections takes ~1s, ending a call makes the sound crack for a few seconds in the most broken and awful way (while locking the UI in place for the duration), it refuses to understand what the browser’s back button is for, there are plenty of slow downs when using the chat... Surprisingly enough, though, the video part seems to work just fine, everything else, however, is a headache-inducing experience.

And I refuse to switch browsers just to use this disgrace of an app. If it’s supposed to work on the web it should not care which browser I’m accessing it from, otherwise a native app (read: not webview-based) should be made available.

>>okayju+wd2
Good to know. I haven't used it on Mac yet, just Windows and Linux PWA.