Seriously, I see zero point of shipping old/buggy chrome bundled with the app (aka "electron") for purpose of accessing some centralized service. PWA is the way to go here, yes.
https://support.microsoft.com/en-us/office/safari-browser-su...
It's the same in Edge on Windows lol. Their own shit doesn't work on their own shit.
So edgeview2 is basically windows only for now, and any future port will mean they'll have to maintain multiplatform support. And guess this announcement implies that they won't port it to Linux. But why do away with the "free" multiplatform compatibility of electron? The official reason was for increased performance, but it's hard to see how electron was the bottleneck considering how badly Teams run even compared to your average electron app. I mean Microsoft has built the best performing electron app I've ever used, vscode!
I'm probably missing something though, and I'm sure there are tons of good reasons for going the edge webview route, but it's still pretty confusing to me!
They were planning on maybe releasing the linux port around the end of 2021, as they were prioritizing the mac port first.
But I don’t think even the mac port has been released yet... So it kind of makes sense for the Teams team (ha!) to just not bother with a linux release if the runtime they are developing on isn't even on the release roadmap yet. Though I guess that makes the switch from electron even more confusing.
https://github.com/MicrosoftEdge/WebView2Feedback/issues/645
https://techcommunity.microsoft.com/t5/microsoft-teams/teams...
Edit: baffling downvote?
Edit: the Adobe website claims you can do form fill and sign of PDFs from within a browser, but it's never worked for me. Recently had to initial every page of a 78-page PDF, which my fairly beefy machine struggled a bit with (it was truly painful on my partner's lower spec machine), I'm curious how feasible that would be in a browser.
The non-nerds also absolutely notice when some stupid Electron chat app makes their laptop hot and takes their battery life from 16 hours to 2.5 hours (ahem, Discord when using voice and/or video chat). Proponents of that tech claim normal users don't notice, but 1) they definitely, 100% do, and 2) more than one might think are even able to figure out which app, specifically, is responsible, not just "my machine's slow and battery's dying fast and I don't know why" (it's usually not exactly rocket science).
My system tray has Slack, Discord, Teams, and VLC pretty much all the time. My taskbar often gets rather loaded with how I switch between workflows, and I've already got the Outlook PWA stuck there doing nothing. I was really hoping I could eventually have a native Outlook electron app (I feel a bit iffy installing a third party solution), but instead I'm gaining another app that sits there 90% of the time doing nothing.
Also what is up with Microsoft's redirect-through-15-domains authentication. Completely unreasonable for anyone that has their browser set up securely.
Really?
For a while I have contemplated creating a lightweight native version of Teams. According to the Teams API it should be possible, I believe
It can simply be c#, no need to go any deeper. But it would be a huge boost in performance
MS certainly is using WPF in some areas (Dynamics 365 client framework comes to mind)
Every time I watch the WinUI community talk it seems like trying to sell us the platform, after all the mismanagment with UWP.
The sad part is when asked about why features X, Y, Z from Forms or WPF still aren't coming in WinUI, they mostly react as if hearing about the said feature for the first time. That is how well the team knows the frameworks they are trying to replace.
WinUI3 good news: it's open source! You can see it on github.
Bad news: it's only just made 1.0, and because it's on github you can see that the team devoted to it is absolutely tiny.