Dear neosunset, go make .NET advocacy elsewhere, and stop identifying yourself with the platform.

Thank you very much.

Uno is a third-party open-source project. It is not related to UWP beyond the fact of being a .NET GUI framework.

It's like complaining that a particular Yamaha bike is bad because a Yamaha digital piano of particular model is bad.

Do take pills before posting, thanks.

Not only do I have taken my pills, I am well aware of what abstraction layer Uno makes us of, when deploying on Windows.

Which if you had done the same, instead of being hurt in your .NET feelings, you would also be aware that what differentiates Uno from Avalonia, is that the former offers a migration path for UWP developers, while the latter does the same for WPF developers.

I said enough times "how high?" when Microsoft shouts "Jump!", since MS-DOS 3.3 was new on the market.

So if you cannot face criticism, well, that is on you to get used to.

And if trolling me makes your fancy, I hope you have been equally trained on BBS and Usenet on their darker days.

Uno Platform maintainer here - Uno is compatible with both WinAppSDK/WinUI and UWP API sets. Our default project templates have been on WinUI for two years now, UWP mainly being supported for temporary upgrade scenarios to WinUI.

Nope it is not.