Be careful what you wish for. I recall when Visual Studio switched to from native to managed (VS 2005?) and it was brutal. It was sluggish, crashy, with weird W

Be careful what you wish for. I recall when Visual Studio switched to from native to managed (VS 2005?) and it was brutal. It was sluggish, crashy, with weird WPF UI bits thrown in here and there to support some oddball feature. As for C, maybe you meant C++? Kicking out a modern, complex, desktop, web/network-centric application in C is just begging for trouble. Particularly given all the headline grabbing research MS has done into how error prone manual memory management has been in their organization [0][1] Actually, it doesn't really seem like a language issue, does it? You can have a terrible app in C/C++/Rust/Go/JS, any language, you name it. Even electron seems a little like a scapegoat - e.g., VSCode and (previously) Atom are examples of "js-on-the-desktop crap" that are surprisingly solid. It's not the language that's the problem, and it's not (arguably) the underlying framework. The app just sucks. If Teams were written from the ground up in C# or C and had the same functionality (or lack of functionality), it would still suck. Teams, as a product, is just sub par compared to other offerings. Even so, it's good enough for the majority of Microsoft's enterprisey and/or locked-in customer base since it's so well integrated into everything else they offer. [0] https://msrc-blog.microsoft.com/2019/07/18/we-need-a-safer-systems-programming-language/ https://msrc-blog.microsoft.com/2019/07/18/we-need-a-safer-s... [1] https://www.zdnet.com/article/microsoft-70-percent-of-all-security-bugs-are-memory-safety-issues/ https://www.zdnet.com/article/microsoft-70-percent-of-all-se...