2 ms·
I think so much of it was also Microsoft realizing they need a really good answer for "why doesn't Win32 work on this Windows?" They may have thought they could
by WorldMaker 7y ago
I think so much of it was also Microsoft realizing they need a really good answer for "why doesn't Win32 work on this Windows?" They may have thought they could do a transition like with the jump from Win16 to Win32 in the Win32 to (proto-) UWP jump in Windows 8, but they partly forgot how long they supported back compat for Win16 applications and they partly forgot that Win32's lifetime was more than triple Win16's and that means a lot more apps that people care about possibly losing.
It took a concerted push in Windows 10 to remove most of the "seams" between UWP and Win32 (to the point where now you can even have UWP Islands inside of Win32 apps). We're also seeing years later the fruits of labor to better emulate Win32 on ARM in the latest Windows 10 on ARM builds.
Though now with Chromebooks gaining popularity they are in danger of being too late again even though now they have an answer to "Can this Windows run Win32 applications, too?" because Chromebook and the increased market shares of iOS and Android have left an increasing number of people wondering what they need Win32 applications for. (The rumors that Microsoft might not even brand whatever this "Modern OS" project is as "Windows" and it may not even refer to current Windows on ARM efforts seems to maybe imply that Microsoft really is too late back to this market that they tried to enter earlier.)