Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

MS Teams Switches from AngularJS to React, Ditches Electron.

twitter.com

Post reply on HN
Print view View original

11–20 of 73 posts

Re: MS Teams Switches from AngularJS to React, Ditches Electron.

#11

Post by kunagi7 »

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.

Re: MS Teams Switches from AngularJS to React, Ditches Electron.

#12

Post by fuzzy2 »

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

It is not switching from Angular 2+. It truly is still AngularJS. Very different and an incredible leap.

Re: MS Teams Switches from AngularJS to React, Ditches Electron.

#13

Post by qixv »

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 returning to work and having to use Teams again.

Re: MS Teams Switches from AngularJS to React, Ditches Electron.

#15

Post by treespace8 »

fuzzy2 wrote: post #10
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?

On a single PC it probably wouldn’t matter that much, but if distributed at scale, the savings in bandwidth could be enormous. Electron is quite large after all. Teams shipped with incredibly outdated versions of Electron for a very long time.

Keeping up the latest electron is f@$king impossible.

It takes months/years to get all clients updated. By then you are already running on an outdated version.

Re: MS Teams Switches from AngularJS to React, Ditches Electron.

#17

Post by treespace8 »

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

When even Microsoft isn't writing native desktop apps anymore, you know it's dead.

Re: MS Teams Switches from AngularJS to React, Ditches Electron.

#18

Post by manquer »

qwerty456127 wrote: post #9
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?

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

They could always fork electron, it would have been first thing to do, unless they are expecting to do lot of radical changes which is quite hard to do on electron perhaps

Re: MS Teams Switches from AngularJS to React, Ditches Electron.

#19

Post by jmkni »

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 to each other.

Also, I couldn't find a way to build a normal Windows installer with Electron (if there is please let me know), but was able to use Wix to build one for my WPF/WebView2 app.

Re: MS Teams Switches from AngularJS to React, Ditches Electron.

#20

Post by manquer »

treespace8 wrote: post #15
fuzzy2 wrote: post #10

Earlier quoted context omitted.

On a single PC it probably wouldn’t matter that much, but if distributed at scale, the savings in bandwidth could be enormous. Electron is quite large after all. Teams shipped with incredibly outdated versions of Electron for a very long time.

Keeping up the latest electron is f@$king impossible. It takes months/years to get all clients updated. By then you are already running on an outdated version.

Is integrating auto-update functionality not standard part of distributed application tooling by now ?
Post reply on HN