That’s my suspicion too. And I believe they did the same thing with Teams and hired some interns who are learning Agile to rapidly deliver “feature”.
At this point, I'd prefer an Azure OS that I could install locally and have the Windows team slowly transition to supporting Wine, improving Linux DEs/Wayland (or even create their own DE), since I believe that they're using some Wayland compositor (mutter?) for gWSL anyways, and contributing to the Linux kernel, which they're already doing to some degree. I genuinely don't know how feasible that is and I'm aware it's wishful thinking, but a person can dream.
Then again, it would probably be to the Linux community's detriment and they'd just do the same scummy Bing/telemetry/dark pattern crap to foster ad revenue.
That just runs completely counter to all the Dev Experience marketing you get from them. It feels like Widgets were slapped together by the kernel team at the last minute.
WinRT is basically the evolution of this, going back to the design board as if .NET never happened, hence .NET Native and C++/CX abstracting what is basically COM + IInspectable + .NET metadata instead of TLB + App Identity.
WinRT eventually became UWP, as they improved the developer experience, only to kill .NET Native, replace C++/CX with C++/WinRT (similar dev experience as using ATL), and move that infrastructure on top of standard COM on Win32 side.
So now you have classical COM, and Windows Runtime components are the modern COM.
Meanwhile DevDiv seems to have had enough of this and decided to focus on .NET with cross platform experience, and Web technologies, hence why even Visual Studio is quite lacking on WinUI tooling.
[0] - If they really cared they would have doubled down on it like Android and ChromeOS did, and all those C# 7 - 11 performance improvements would have been done at the time.
After the mismanagement of WinRT, finally fixed with UWP on Windows 10, instead of improving the .NET Native and C++/CX experience, they created Project Reunion, deprecated .NET Native and C++/CX, replacing them with lesser tooling, pivoted Project Reunion into Windows SDK, and are years away of reaching feature parity with UWP, let alone Forms, WPF, MFC.
The current team seems composed by interns without experience on previous Microsoft frameworks, while the more experienced folks seem to have moved into Azure, Google or Amazon, from their twitter feeds.
Just have some fun going through the WinUI, CsWinRT, C++/WinRT, WinAppSDK, Win2D, and see the endless amount of bug tickets, measured in thousands.
Blazour seems to be the new kid in town, to the point of even trying to push it inside MAUI as pseudo-Electron replacement.
Meanwhile the other business units are focused on Web or Android.
It looks like "Azure OS" is the new Windows.