They've absolutely lost their roadmap, and I think they've also lost the distinction between solving a problem that Microsoft has versus a problem the users have.
There's also the tension between dotnet core trying to be properly cross-platform vs having it actually support the various Windows toolkits. They've historically been welded into the build system as first-class citizens, rather than optional packages, which causes trouble as soon as you do a cross-platform build. WinUI3 goes halfway to fixing that by being installable as a package, but still relies on "<UseWinUI>true".
And they've never quite dealt with having their platform be eaten by the web and the Apple Store / Google Play Store. See https://blogs.windows.com/windows-insider/2021/10/20/introdu...
There's also the tension between dotnet core trying to be properly cross-platform vs having it actually support the various Windows toolkits. They've historically been welded into the build system as first-class citizens, rather than optional packages, which causes trouble as soon as you do a cross-platform build. WinUI3 goes halfway to fixing that by being installable as a package, but still relies on "<UseWinUI>true".