21 ms·
> Bottom line, if you don't like it, don't use windows. > Or if you use windows because it has value to you, you > have to play by MS rule or hack around. Like
by scholia 11y ago
> Bottom line, if you don't like it, don't use windows.
> Or if you use windows because it has value to you, you
> have to play by MS rule or hack around. Like with cars.
UWP apps are written to use the Windows Runtime API.
Traditional programs are written for the Win32 API.
If you don't like the rules for UWP, don't write games for it. Nothing stops you from writing games for the Win32 API.
- pjmlp 11y agoProject Centennial will help move the remaining Win32 into UWP model.
- leereeves 11y agoFirst Microsoft will have to move people to Windows 10 (currently at less than 15% market share).
- sccxy 11y ago34% Steam users run Windows 10. http://store.steampowered.com/hwsurvey http://store.steampowered.com/hwsurvey
- leereeves 11y agoA more relevant statistic, thank you, but also a reminder that Steam is another obstacle to UWP. Would developers prefer their games to be on Steam or on the Windows Store?
- scholia 11y agoTheir choice: they could do either, neither, or both. Presumably Tim Sweeney wants to do UWP or he wouldn't be making such a fuss about it.... Maybe some developers will think it's a good thing if Steam has some competition?
- scholia 11y agoTrue, but Windows 10 has more than 200 million users, which makes it bigger than all versions of Mac OS X and Linux combined. The US DoD has already started to move 4 million users to Windows 10, which is a good sign. Most businesses will be planning to move by 2020, when Microsoft stops supporting Windows 7 (though I expect a few daring souls will be hoping for an XP-style extension). So, Windows 10 is slightly ahead of track for a billion users at the moment. Just how many gamers are we talking about here?
- wolfgke 11y agoHow can I allocate executable memory to write a JIT compiler under UWP?
- pjmlp 11y agoMost likely by having the right appx permissions to do so. Project Centennial is supposed to allow for 100% compatibility with existing Win32 APIs. This is from last BUILD. https://channel9.msdn.com/Events/Build/2015/2-692 https://channel9.msdn.com/Events/Build/2015/2-692 https://channel9.msdn.com/Shows/msdevshow/Episode-56-Project-Centennial-Win32-in-Appx-with-John-Sheehan https://channel9.msdn.com/Shows/msdevshow/Episode-56-Project... This upcoming BUILD might have more talks about it.