>More fluid and responsive app interactions: Reducing interaction latency by moving core Windows experiences to the WinUI3 framework.

I think this is good, because they're talking about removing (hideously inappropriate) react and other web technologies from core OS components, and using proper native OS calls instead. But I'm not familiar with WinUI3. I only know Win32. Is WinUI3 a flash-in-the-pan system like their other UI attempts, or is it decent and stable?

▲

xeeeeeeeeeeenu 7 hours ago | parent | next [-]

> Is WinUI3 a flash-in-the-pan system like their other UI attempts, or is it decent and stable?

If you stay in the happy path, it's decent, better than it used to be. Microsoft does seem committed to it, they're slowly converting Windows apps to WinUI 3.

That said, the team is clearly understaffed; there are long-standing unresolved bugs, just search for "memory leak" on their GitHub issue tracker. Also, native, non-.NET support is definitely an afterthought, it's barely documented and the tooling is super awkward. But at least, unlike WPF, it exists.

	▲	jiggawatts 5 hours ago \| parent [-]
		WinUI 3 was a step back from WPF in technology, because it panders to the virtually non-existent Microsoft .NET mobile app market. To remain compatible with Android and iPhones they removed or simplified a bunch of features, ironically stripping out HDR support just when practically all phones got wide gamut and HDR, OLED screens, etc. In the era when mobile phones are getting amazing, Microsoft is still racing towards the bottom along with every laptop maker other than Apple.

▲

userbinator 5 hours ago | parent | prev [-]

That sounds like the same bullshit they spouted when they tried to shove the "modern app" crap with Win8.

There's nothing wrong with Win32 (and everything wrong with the newer stuff); "interaction latency" was just fine on a single-core 33MHz 486 running Windows 95.