4 ms·
I don't have much hope for this. Their "own" edge WebView2 tech is powered by chromium, the same as what powers the old electron. And "based on react not Java
by wkat4242 4y ago
I don't have much hope for this.
Their "own" edge WebView2 tech is powered by chromium, the same as what powers the old electron.
And "based on react not JavaScript"... React is a framework in JavaScript.
Neither are fundamental improvements. They're more branding than anything.
None of these explanations make any sense. What would make sense is if their team stops prioritizing glossy new features and optimizes the core code. Just like the VS Code team has done from the very start.
Perhaps this is what they are doing and they're trying to peddle their WebView in the process. If it's just those 2 changes they mention I'm sure the result will be underwhelming. As always with Teams so far.
- etempleton 4y agoMore likely Teams was written quickly as a response to Slack and some poor decisions were made along the way. Performance and resource usage are my two biggest issues with Teams so this is a welcome update. I don’t think Teams is perfect, but it is useful for what it is and generally is good enough.
- happymellon 4y agoPerformance and resource usage is bad, but it is a far cry from being the biggest issues I have with Teams. Inability to handle formatting of messages is a big one. It will decide that my codeblock should actually be two, and it is impossible to merge them. Scrolling in opposite directions depending on the tab. Making up another SharePoint site with each group team chat so that we can ensure we silo our data and never find it again.