MS Teams Switches from AngularJS to React, Ditches Electron.

Post by exoque » Fri, Jun 25, 2021, 6:20 PM UTC

enlightens wrote: post #16

The 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...

Post by jerhewet » Fri, Jun 25, 2021, 6:23 PM UTC

Post by MR4D » Fri, Jun 25, 2021, 6:27 PM UTC

kunagi7 wrote: post #11

qwerty456127 wrote: post #8

"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

Skimming through the Tweets, it seems like the rest of the online Office suite uses React and Teams was the outlier using Angular. Somehow it makes sense to use the same framework for everything and save resources.

Post by godelmachine » Fri, Jun 25, 2021, 6:29 PM UTC

qixv wrote: post #13

olyjohn wrote: post #5

I hope this also takes care of the battery life issue. Teams video meetings will take my 8 hour battery life, and suck it all down in under an hour. Zoom would not even put a dent in my battery any more than me doing my regular work.

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…

Post by moogly » Fri, Jun 25, 2021, 6:31 PM UTC

jmkni wrote: post #19

SigmundA wrote: post #6

Wonder 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?

I'm using WebView2 on a project at the moment, inside a WPF (dotnet core) app. One thing I've been having some fun with is the ability to host a REST dotnet core API inside the same application and then calling Javascript functions/updating the UI on an HTTP request. It's very handy if you have multiple applications on the same machine (or the same application on multiple machines on a LAN) and you want them to talk…