undefined | Better HN

0 pointspjmlp1y ago0 comments

If it was only Skype, Windows development has turned into a mess, it appears teams are filled with newly grads, without any background on Windows development, or Windows developer culture.

That is why there are now Webview2 usage all over the place, and after 5 years WinUI 3.0 is still behind the WinForms, WPF and even MFC development experience, even though it should have been a plain port of UWP/WinUI 2.0 into standard Win32 infrastructure, so adding almost another 10 years on top (WinRT platform came out in 2012).

EDIT: it was actually 2012, not 2014.

0 comments

4 comments · 2 top-level

DanielHB1y ago· 2 in thread

I imagine internally they have a hard time staffing the Teams project. Like VSCode is a WebView2 project but it is miles ahead of Teams in quality. At least on the client side features seems far more complex too.

Teams used to use Angular 1 and I think they are still migrating out of it. Microsoft would need to pay me a lot of money to want to dive into that mess. I imagine there are a lot of devs who would love to be VSCode core developers though.

pjmlpOP1y ago

It was also React Electron for a while, but that isn't the only issue with Teams, even if we comparing them running as pure Web application across browser tabs, Teams, Slack, Discord,.....

I really don't know what the Teams team does all day long.

DanielHB1y ago

Dealing with old crappy codebases can really tank a product, especially if you don't have management support to fix the broken practices.

I imagine the Teams project gets a lot of pressure to deliver features instead of fixing the underlying problems. While the VSCode project probably only occasionally gets a push from upper management (like to add copilot stuff)

Delivering features on top of an unmaintainable mess just makes the mess bigger.

kennysoona1y ago

This is why they tried to remake the Windows interface to be more Mac like as well. What a disgrace.

j / k navigate · click thread line to collapse