Cool, maybe they'll solve the problem of Teams freezing up constantly someday.

That does not happen, even with the beta grade Linux version on Arch (as I run it)

You may have a rubbish internet connection. If you are using a VPN with a slow internet connection, investigate a split tunnel. Teams traffic involves only three IP ranges so it is easy to split out and route direct to shave a fair bit of latency.

Other issues will require more investigation but they are local to you.

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

Try disabling gpu rendering.

I think that's the generic solution to Electron apps issues :-))

That works OK, even on Linux (anecdotally)

I will kiss you if this works.

It might depending on platform. On my windows laptop, I can videoconference without GPU accelleration. Windows 10 has an impressive software fallback for gpu rendering (WARP), they could be using that.

Agree if your computer resources are being utilized over 70 percent teams becomes a nightmare. They could have written it in c++ in the same amount of time and had that thing running smoothly.

Rewriting it in C++ to magically solve problems. Good job, engineer.

> Rewriting it in C++ to magically solve problems. Good job, engineer.

Well it's a lot easier to make an app perform well in C++ than electron.

They should at least have for the VS Code team to help. That's one of the best performing Electron apps, it's strange MS never adopted those practices company wide.

Or they did, and it has more to do with different things happening on the network layer of individual machines.

Hmm when I compare the two in terms of CPU / Memory usage and speed, Teams is one of the worst performing electron apps on my system, and VS Code one of the best. I don't think this is just network related (and I have a 600/600 connection anyway).

Either way, even if this was the reason it would prove that Electron is not a good fit for an app like this.

Sounds like a lot of shit rolling downhill.

The issue with teams is performance. Teams is a relatively simple application. C++ is extremely common and well known, would have been a better tool for the job. That’s called engineering when you actually care about the quality of the product.

Calling that engineering reminds me of things I said while being in college before I had any real experience.

Why? The teams app is an example of poor engineering. I don’t see how you don’t realize this.