[pjmlp]

Yeah, if one wants to have fun debugging all the issues that are still open since Project Reunion was announced in 2020, with less capable tooling than .NET Native and C++/CX, specially fun having to deal with CsWinRT and C++/WinRT, the latter already in maintenance, stuck in C++17, as the team is now having fun with Rust/WinRT.

At least Native AOT might support WinUI in .NET 9, something to look forward to, for anyone that still cares outside Redmond.

[m_mueller]

I think the alphabet soup thrown around in this thread alone is indicative for what‘s wrong with Microsoft‘s native user interface story…

[pjmlp]

I can throw similar alphabet soups from other ecosystems, either one is in and gets them, or not.

[tonyedgecombe]

Not really. Apple has a much more consistent story on UI frameworks.

[pjmlp]

Not being around Mac OS long enough?

[m_mueller]

such as? If I remember correctly (has been a few years), over the last 15-20 years there were

iOS: UIKit -> SwiftUI

MacOS: AppKit -> Catalyst -> SwiftUI

there was definitely some churn within each one of those from version to version, but no complete rewrite needed afaik.

[pjmlp]

I advise then to pay attention to Apple developer podcasts for rants regarding each of them, and porting issues, you can start with ATP.

[tonyedgecombe]

I wouldn't even include Catalyst in the list. It is only relevant to a small subset of developers.

[tonyedgecombe]

My first Mac was an SE/30.