Per VognsenSomehow I doubt it. Headline: "Microsoft is finally getting its native Windows UI platform act together with WinUI 3 and WPF."
Ritesh Oedayrajsingh Varma@pervognsen as someone who has been through all of this, my feelings can be perfectly summed up with this gif
@rovarma My honest reaction: I didn't know there was a WinUI 1 or WinUI 2!
suushikijitsu@pervognsen @rovarma
WinUI 1 was a controls library for UWP that was used internally within the Windows division at Microsoft on some of the built-in apps in Windows 10 for a while. It was never released to the public or even discussed publicly (prior to the public release of WinUI 2) AFAIK, so it's no surprise you didn't know about it.
WinUI 2 was an updated version of that controls library which was released publicly as an open source project.
Confusingly WinUI 3 comprises not only a further updated version of the WinUI controls library, but the entire UI framework underneath it including the layout and composition layers, all of which were forked from their equivalents in UWP XAML and "lifted" out of the Windows codebase. So it's not only a newer thing but a different category of thing than what WinUI 1 and 2 were ...
@pervognsen @rovarma
... except that after the release of WinUI 3, "WinUI 2" was sorta retconned to mean the entire UWP XAML stack, parallel to WinUI 3, not just the controls library on top of it.
... except that after the release of WinUI 3, "WinUI 2" was sorta retconned to mean the entire UWP XAML stack, parallel to WinUI 3, not just the controls library on top of it.
@suushikijitsu @rovarma Classic. And here I thought I thought they were just pulling the old Windows NT 3 trick where 3 is the first version.