you have a lot to learn about computers if you're still dishing out the "it works on my machine so it's not a problem" excuse

they gave a credible theory to back it up though.

I'm only 50 and been messing around with them for about 40 years.

My point was that even on a precariously supported platform (my Arch Linux computers), the software works fine - ie as proscribed. MS Teams is used by a vast number of people and has a habit of working OK for them.

It’s difficult to fix issues on compromised machines, for example. Or buggy VPN. Etc.

Sometimes it really is a specific person’s issue, and sometimes there are a lot of them so it can look like a vendor issue.

Of course, sometimes it is a vendor issue.

There is a percent range where it is difficult to differentiate. Made worse by a large user base.

Same freezing problem, company issued laptop 100mbit internet connection. Same feedback from hundreds of people. Half a gigabyte RAM or more even when Teams inactive. Other softwares have solved this problem so I will agree with the opinion that Teams team should put their act together. I will postpone prioritizing Teams ips to the routers.

If the software freezes because of a bad Internet connection, and it can't detect and report the Internet problem, it's still a bug in the software.

e.g. "Slack has lost connection... We'll try to reconnect in 30 seconds"

"Works on my machine" is not a serious person's response to anything