We had the teams update at work, with the endless notifications to let me know that a new version was coming, would I like to update early, on the 1st the update will be forced …
And the new Teams is not simply a replacement, no. It’s called “Teams (for work or school)” or something, while the old app is “Teams classic”. Both look the same and are the same sluggish mess. So why exactly did we do all that crap?
All I know is that one of them has a /v2/ subpath on its URL, and the other has nothing.
Oh, and calls work in Firefox one the /v2/ one. That’s an important difference.
What I really don’t know is why they kept pestering me for months to make sure my browser supports the new version (where they know what my browser is, and only published enough requirements to tell IE won’t work) while they only changed stuff that makes it work better on it.
We had the teams update at work, with the endless notifications to let me know that a new version was coming, would I like to update early, on the 1st the update will be forced …
And the new Teams is not simply a replacement, no. It’s called “Teams (for work or school)” or something, while the old app is “Teams classic”. Both look the same and are the same sluggish mess. So why exactly did we do all that crap?
And they would use at least a quarter or your RAM.
uNuSeD rAm Is WaStEd RaM!!!
All I know is that one of them has a /v2/ subpath on its URL, and the other has nothing.
Oh, and calls work in Firefox one the /v2/ one. That’s an important difference.
What I really don’t know is why they kept pestering me for months to make sure my browser supports the new version (where they know what my browser is, and only published enough requirements to tell IE won’t work) while they only changed stuff that makes it work better on it.