The other possible takeaway is that after Windows Phone, Microsoft really has been truly risk adverse when it comes to consumer products, even in areas where they had a lead and could have delivered something no one else could.
> VSCode shows they can execute, but for some reason when the stakes are higher they don't do as well Windows Phone
Windows Phone was arguably very well executed at the software level. Microsoft's troubles with Windows Phone were at the hardware levels and (worse) the economic levels where the phone carriers had already decided they prefer a duopoly and selling three things is one too many things to sell.
(I had more inconvenience moving apps back and forth between WPF and Silverlight in some of the years prior, and even those moves were never from-scratch rewrites. Admittedly that may have left me with more skills to handle XAML changes and write to lowest common denominator XAML, so I am aware of my biases.)
I realize you aren't ever going to agree with me on this, and I don't expect you to. I do think it is still useful for other people to see that there are counter-opinions here.
Not going to bother to list everything that changed, it is public available for anyone to judge.
That's the only "hard fork" between the versions. I know a lot of people (including respondents in neighboring comments) saw the changes between WP8 and WP10 as a big deal "soft fork", but very little actually changed other than a UI library upgrade from 1.x to 2.x. (In .NET; JS was dropped in 2.x and C/C++ developers saw some other shenanigans. But JS and C/C++ didn't exist in WP7 either so none of those developers saw all three "migrations" either.)
I hear a lot from developers that it seemed very fragmented, but working in it at the time, it seemed very "incremental" at best, mostly just upgrading library major versions and dealing with semver major breaking breaks. Sure, that's frustrating when that's not your primary development environment and also you aren't getting paid enough for it because adoption is low, but that is a very far cry from "Microsoft didn't have a good plan". They were iterating hard on it. They made some semver breaks that other library authors in other ecosystems could get away with no problem, even with equally low adoption (looking at random JS libraries here). It's easy to blame low adoption for making those semver major breaks seem more painful and "fragmented" than they actually were in practice, but sometimes it just also looks like that was an excuse to ignore the platform more than a problem for development experience reality. (As you seem to state that you skipped the platform entirely, possibly because you were looking for an excuse to skip it and latched onto the first one you saw.)
[1] Obviously not clear enough for some.
It's one thing to develop versions for Android, iOS, and Windows Phone. It's another if the UX source elements can't be shared within the MS ecosystem Phone, RT, x86 metro apps.
https://learn.microsoft.com/en-us/previous-versions/windows/...
https://learn.microsoft.com/en-us/cpp/porting/porting-to-the...
https://learn.microsoft.com/en-us/archive/msdn-magazine/2014...
https://learn.microsoft.com/en-us/windows/uwp/porting/wpsl-t...
https://learn.microsoft.com/en-us/windows/uwp/porting/w8x-to...
To me it does seem a low target to aim for. VSCode shows they can execute, but for some reason when the stakes are higher they don't do as well Windows Phone, Edge browser, etc. I suppose I could call that corporate self-awareness.