11 ms·
What's the point in doing this for MS? There's no money in it and they'd need a serious team backing it. And by no money, I mean at scale - there are going to b
by viraptor 9y ago
What's the point in doing this for MS? There's no money in it and they'd need a serious team backing it. And by no money, I mean at scale - there are going to be small companies needing something like that and there are going to be huge companies. Huge ones already got a public offer of "pay an increasing tax for XP support" and likely a private "this corporate deal is possible" if they're important enough. The small ones put together, I don't think could collectively fund ongoing xp support.
If anything ReactOS picking up those small companies is beneficial to MS by keeping them in the MS ecosystem.
- richard_todd 9y agoLike a sibling comment mentioned, it wouldn’t be the first time MS has done this sort of thing (XP on certain SKUs of Vista or maybe it was 7). I assume they already have a serious team backing tons of legacy Win32 cruft. So, instead of maintaining that, they freeze it and shift it into a VM. MS gets to cut down modern Win32 to something closer to the UWP subset, and users that want it—-make it an optional subsystem—-get better legacy compatibility than they have had in years. Maybe the 2020 win7 end of life would be a good time to do something like this. I don’t know if there is a good enough financial reason for MS, but from a user’s perspective I think it would be better than the situation today.