Too many burned bridges since Windows 8 came out.
If anything, this is Microsoft confirmation that they are unwilling to fix all the broken issues, and hoping the community will somehow still care.
WinForms and WPF are currently the only viable frameworks for Line of Business application. I have yet to see a WinUI3 application in the wild.
On a side note, I still love WPF after working in it for 10 years. Maybe it's just familiarity, and it's a little verbose at times, but man it's a great framework when you know that you're doing.
One of the biggest problems with WinUI compared to WPF is that DependencyProroperty is implemented as native code, so for .NET developers, there is a huge performance penalty getting or setting any property on control.
https://github.com/microsoft/microsoft-ui-xaml/issues/1633#i...
I read through that github issue a few years ago and with a mix of surprise and disgust knew that I would not be learning WinUI.
Why use a busted incomplete framework missing basic features when there's entire ecosystems of open source cross-platform frameworks being actively maintained and which actually have all the features you need?
Really this is just another UWP destined to be forgotten and scorned.
UWP never had feature parity with neither Forms nor WPF, so already it has a hard sell to businesses.
Microsoft marketing always cool about cool experiences and design, without the actual meat in features.
That is why there were API reboots between Windows 8, Windows 8.1 and Windows 10.
Then comes along Project Reunion, which is supposed to properly unify Win32 and UWP execution models, instead a few months in, they do yet another reboot, that to this day is a shadow of UWP features, endless bugs, and a team that everyone thought was also part of the layoffs, has they were radio silence for months.
GDI32 you say? At least it works.
I've also tried WPF, but it's missing very basic controls that I just don't feel like recreating.