3 ms·
I'm not particularly familiar with Electron and WebView2, but even the Electron blog suggest that WebView2 uses some different IPC formats that can be faster[1]
by lizard 4y ago
I'm not particularly familiar with Electron and WebView2, but even the Electron blog suggest that WebView2 uses some different IPC formats that can be faster[1]. Considering a big selling point of Teams is as a hub for other Microsoft products, and other plugins, it doesn't seem unreasonable that improvements to the IPC would translate to better performance for Teams, in at least many of the expected usecases.
[1]: https://www.electronjs.org/blog/webview2/#performance-discussion https://www.electronjs.org/blog/webview2/#performance-discus...
- wkat4242 4y agoI didn't know about that blog but as far as I get it they mention the IPC just as an edge case that might give a little benefit and mention overall similar performance in their summary: > Electron and WebView2 have a number of differences, but don't expect much difference with respect to how they perform rendering web content. Ultimately, an app’s architecture and JavaScript libraries/frameworks have a larger impact on memory and performance than anything else because Chromium is Chromium regardless of where it is running. Which does indeed make sense, Microsoft is way too focused on adding shiny new features to Teams and too little on its performance. But anyway I hope it does make a big difference. It's really a source of frustration now.