{"id":33897,"date":"2021-10-13T17:13:37","date_gmt":"2021-10-13T21:13:37","guid":{"rendered":"https:\/\/mjtsai.com\/blog\/?p=33897"},"modified":"2021-10-14T08:47:37","modified_gmt":"2021-10-14T12:47:37","slug":"visual-studio-and-teams-get-more-native","status":"publish","type":"post","link":"https:\/\/mjtsai.com\/blog\/2021\/10\/13\/visual-studio-and-teams-get-more-native\/","title":{"rendered":"Visual Studio and Teams Get More Native"},"content":{"rendered":"

Microsoft<\/a>:<\/p>\n

We’re moving Visual Studio for Mac to native macOS UI, which will fix over 100 previously reported issues related to performance, reliability, and product quality. By using native macOS UI, the IDE now works more reliably with macOS’s built in assistive technologies. In this first preview release, we’re giving you a glimpse at the IDE and focused on main features .NET developers use to build applications for the web.<\/p><\/blockquote>\n

My understanding is that this used a cross-platform UI layer [Update: Gtk+<\/a>], not Electron.<\/p>\n\n

Faisal Khan<\/a> (via Hacker News<\/a>):<\/p>\n

Microsoft recently announced that they have reached a whopping 250 Million active users with Teams. Not Word or Excel but Teams is the rockstar of the Microsoft Office suite. But, it has always been plagued with performance issues as it consumes heaps of system resources. Running Teams is a nightmare on computers with less memory to work with.<\/p>

[…]<\/p>

The senior vice president of Microsoft Teams announced<\/a> that Teams would be moving to their own Edge Webview2 Rendering Engine ditching Electron for seeking performance gains. It is marketed that Teams would consume 2x less memory as a result of the transition. It would be called Teams 2.0 and might ship with Windows 11 in late 2022.<\/p><\/blockquote>\n\n

I’m not sure this makes much difference for Mac users, since it’s still built on Web technologies with a bundled browser engine.<\/p>\n\n

Previously:<\/p>\n