Hacker News Reader

To make an app with the same "nativeness" as the "Settings" app, you need to use UWP, or WinUI 2.7+. But not 3.0+.

.. however, you're then stuck in the UWP sandbox, I believe?

(edit: crucially I don't think you can use either of those with dotnet core?)

Why not 3.0+? What’s changed?

The namespace, basically.

They decoupled the UI framework from the OS in WinUI 3.0. The point of UWP was that it used controls and rendering capabilities built into the OS. This resulted in performance regressions and missing features for several versions compared to the 2.8 branch.

Goddamn!

I always wondered why it took until Win UI _3_ to decouple...but I guess this is why.

Reply on news.ycombinator.com