Earlier quoted context omitted.
This (video, specifically) is more likely a codec issue, and perhaps lack of support (or nonexistence of) for hardware accel paths in it on your hardware.
I'd also like to see more info on this, Teams will consistently bring a quite powerful laptop to it's knees. Posting something to chat while in a meeting will take 5-10 seconds, i have never seen it work instantaneously.
MS Teams Switches from AngularJS to React, Ditches Electron.
51–60 of 73 posts
Re: MS Teams Switches from AngularJS to React, Ditches Electron.
#52The linked tweet says that they're switching away from Angular, not AngularJS. These are two entirely different frameworks. https://en.wikipedia.org/wiki/Angular_(web_framework)#Differ...
"AngularJS" is more commonly specified as "Angular 1" these days. Without specifying 1 it usually means the latest version of "Angular" which started with only 2+
Re: MS Teams Switches from AngularJS to React, Ditches Electron.
#53Like many in that thread, I'm wondering how WebView2 will work on Linux or Mac. Will it be a PWA or will they build a native shell around native web views for each platform?
Apparently, Microsoft is looking to port WebView2 to both macOS and Linux: https://github.com/MicrosoftEdge/WebView2Feedback/issues/131... https://github.com/MicrosoftEdge/WebView2Feedback/issues/645
I wonder what form a WebView2 would take on macOS and Linux. Some of the commenters on that issue mentioned that they were interested in using it with MAUI/.NET [0] but they could even produce a lower level, C++ component for interop with other environments, which would be pretty interesting.
If I could build small, fast desktop cross platform apps with just .NET though, I'd still be interested.
Re: MS Teams Switches from AngularJS to React, Ditches Electron.
#54Re: MS Teams Switches from AngularJS to React, Ditches Electron.
#55Earlier quoted context omitted.
This. Also, my Teams is _really_ slow. When I, during a video meeting, decide to paste my clipboard into the chat to share an URI, it takes upwards of 10 seconds from when I first push the chat button to it having loaded, and having loaded the input field to having sent the message. It is the same when loading a chat with a new person. It is just _slow_. Thankfully it is weekend now, so I have two full days before re…
Not forgetting to mention Teams is a memory guzzler Just boot it up and puff, 500MB gone into oblivion
Re: MS Teams Switches from AngularJS to React, Ditches Electron.
#56"Ditching Electron" is a clickbait - it doesn't go native, just switches to their own clone which seems very reasonable to me as long as they are capable and willing of maintaining it. Switching from Angular to React seems weird. What for? AFAIK the only way React is better is there are more developers familiar with it. I wonder if they considered switching to PHP instead /s
Re: MS Teams Switches from AngularJS to React, Ditches Electron.
#57Wonder why WebView2 would be any better than Electron? They are both Chromium based and if kept ups to date should be almost identical, would it just be saving disk space and sharing some memory since it would be using a single install of the browser engine?
> Wonder why WebView2 would be any better than Electron? Because its under their own control. Using a platform you control is great if you actually have the resources to maintain it.
Re: MS Teams Switches from AngularJS to React, Ditches Electron.
#58Earlier quoted context omitted.
> Wonder why WebView2 would be any better than Electron? Because its under their own control. Using a platform you control is great if you actually have the resources to maintain it.
Don't they own GitHub which employs most of Electron's contributors?
Re: MS Teams Switches from AngularJS to React, Ditches Electron.
#59Earlier quoted context omitted.
When even Microsoft isn't writing native desktop apps anymore, you know it's dead.
Is that why MS Teams is so glitchy? I really wish companies don't abandon native.
Re: MS Teams Switches from AngularJS to React, Ditches Electron.
#60"Ditching Electron" is a clickbait - it doesn't go native, just switches to their own clone which seems very reasonable to me as long as they are capable and willing of maintaining it. Switching from Angular to React seems weird. What for? AFAIK the only way React is better is there are more developers familiar with it. I wonder if they considered switching to PHP instead /s
It is not switching from Angular 2+. It truly is still AngularJS. Very different and an incredible leap.