Whatever is happening there, is quite clear that the COM / C++ folks are driving it all again.
They are so deep into it, that any complaints from .NET devs ends up being that "it isn't so hard to write a bit of C++ with the clunky C++/WinRT, or [ComImport]", naturally the advice people like to get.
Ah and the fact that they push Win32 with bare bones C++, where each developer has to create their own MFC like frameworks, is yet another example how things went wrong.
> Microsoft Surface Duo
That's codenamed Andromeda. [1]
And yes, was planned to be a Windows SKU before mobile Windows utterly exploded.
[1] https://www.windowscentral.com/surface-duo-andromeda-windows...
Then something happened in the late-spring 2021 when the shell team all suddenly disappeared - around the same time as Bill Gates' divorce announcement (coincidence? I think not!) and the Windows org's leadership decided to make the bold move of copying-and-pasting Windows 10X#'s cut-down shell, intended for mobile devices, into the full-fat enterprise and desktop SKUs of Windows 11 and call it a day.
My sources and former work-colleague friends at MS tell me that the current shell team (they should call it a fossil team at this point considering it seems there's nothing left of it) is very, very aware of the huge backlash over the removal of essential features like repositioning the taskbar and having individual taskbar buttons, but don't expect a quick-fix - I get the feeling some hotshot PMs will try to use this occasion to pitch their own unique new (and unproven...) concepts on how the shell should work, instead of doing the big fat `git reset HEAD` back to a late-2019 commit that they should be doing... le sigh...
[1] (which runs Android... which is further evidence something went really wrong with the wave-function collapse around 2016)