timppu: About comparisons to Chromebooks... don't Chromebooks allow running Android applications that are
not from the Google Play store? I know all my Android phones and tablets can run non-Google Play apps just fine, e.g. those Android games I've bought from Humble Bundle. It is disabled by default for security reasons, but you just change the setting and you are all set, you don't have to pay Google $50 extra in order to run non-Google Play apps etc.
Unless Chromebooks don't have this ability, I don't see why the comparison is made. Android isn't really a walled garden, similarly like iOS, Windows RT and Windows 10 S are. You are not locked only to Google's store.
I was unaware of the Windows 10 S restricting installations to the Store. That said, I hope that is not true or will be dropped on the actual release, as this limits the OS's potential far than it already is. Honestly it isn't a good idea at all.
timppu: People can develop also for e.g. iOS even though it is walled garden. I don't see how that would somehow guarantee Win32 is here to stay forever.
That's because for a long time, MS has focused on backwards compatibility as a reason to pick up their OS. iOS on the other hand needs its apps to be updated per major release, and now there cannot be any 32-bit apps remaining as the OS will soon entirely run 64-bit apps only. Meanwhile, Windows 10 has a 32-bit and a 64-bit edition, whereas Mac only has 64-bit and Arch Linux will kill 32-bit later. Win32 apps and games, continuously updated and developed and used, and the goal of axing it, they don't seem to click together.
And much much later, when they have alienated people enough from Win32, kill it completely.
That's the problem, alienation. Honestly, besides 'develop for more platforms at once', UWP applications don't really have a definitive advantage over Win32 apps. They're sandboxed which is an advantage in that if an app does something it will end up doing it only in that limited sandbox, and a disadvantage in that power tools that rely on accessing other applications' data or system files cannot be developed in UWP, which is one thing. It's also hard to backup their data, let alone the application itself. It will be a while until they catch up on any of this.
In a similar way like they did with support for old MS-DOS programs. First they offered the option to run your old MS-DOS apps and games in Windows 95/98/98SE (and ME? Not sure, I've never used it), but with XP they finally felt it was safe to kill MS-DOS support completely.
Tested that on a XP VM, and you're right. I thought for a while that DOS applications are fine on XP. Thanks for the tip-off.
They had a different motive (technical reasons) to kill MS-DOS support and steer people away from MS-DOS (even for games), but the plan could be similar for steering people away from Win32 apps,
That begs the question, what are they going to say if they were to move Win32 away this time?
So far, right now, it's positioned as a Chromebook competitor. But if it does expand to what both of you say, a strategy to kill off what makes Windows Windows, then the future of the PC is going to be uncertain from then on. While they have the power to do that, I trust that they are not going to take it as far as this simply because it is a bloodline.
On second thought, making it harder and harder sounds like what is being done for 16-bit applications on the 32-bit systems, in which you have to install a Windows component to run them on at least Windows 8, I believe.