Office uses React Native
C#, NET, WPF are un-native, and for "fun". If it feels native, talks native, and sells better, then...
Suppose, you tell developers, to make the best Windows apps, to use -
2000’s - use MFC, OLE, ComObjects!
2002’s - use ActiveX, ATL and light-weight CAB files in Internet Explorer!
2003’s - use WinForms!
2006’s - use WPF!
2007’s - use Silverlight instead of HTML, for WPF-based C# apps.
2011’s - use WinUI (non-Xamarin version of WPF)
2012’s - use WinUI Metro (or some cobbled-up WPF theme, using paid WinForms themes)
2015’s - when are bug-fixes for WinForms, WPF? Windows 10 is released!
2018’s - use Xamarin for Mobile! use Blazor!
2020’s - use WinRT (and whatever new rubbish database, whatever rubbish new WinRT features)
2021’s - when are bug-fixes for WinForms, WPF? Windows 11 is released!
2022’s - WPF is now EOL, use WinUI
2024’s - use WinUI1 (and whatever XAML renaming of namespace required)
2025’s - when are the bug-fixes out for WinUI, WPF? It’s still not fixed in Windows 7/8/10/11.
Delphi - use VCL (equivalent of MFC dialogs) and hold my beer.
As Visual Studio evolves, one wonders, if Microsoft uses it’s own frameworks, why won’t it use WPF or XAML? Instead it uses React2.
One is that the Windows team has historically been wary of .NET and the overhead of the Common Language Runtime (CLR), preferring to develop in C++ for performance reasons (Emphasis added).
Windows framework are for suckers.
Delphi developers looking for a reactionary UI framework, there is UniGui or D2Bridge, unless you want to wonder around .NET development-desert.