Also GTK4 is GPU accelerated whenever possible, with really well mantained Rust bindings for it I think the only thing missing would be macOS which I'm not sure what solutions are there.

Another option in this front could be Flutter if write-once run-everywhere is a need for the project. Another advantage is that it's not only GPU accelerated but it's also retained mode.

Nobody loves native WinUI, not even Microsoft.

Which is kind of a shame. But it's the result of years of product management neglect as well as the pull away from desktop UIs to web UIs.

They only have themselves to blame, after the rewrites their forced their hardest advocates to go through, each one with worse tooling, dropping the UI designer, .NET Native and C++/CX along the way.

Native AOT still can't compile WinUI, while C++/WinRT is like doing ATL in 2000, while bug issues grow exponentially.

Only WinDev themselves, and WinUI MVPs, can still believe this is going somewhere.

The rest of us have moved on.

So is everything written in Apple native UI frameworks since 2009.

And Android and QT and GTK and Chrome and Firefox and etc...

The article is talking about the same generic hybrid GPU-accelerated rendering architecture that everything uses. Seemingly the only "new" part is "in Rust!"