We need to add a WinRT version specifier to denote code that is specific to the Windows Runtime platform that is available on Windows 8 and later. This platform is distinct from the Win32 API's by the fact that it is OO and COM. This should be considered a necessary first step to supporting WinRT.
Comment #1 by andrej.mitrovich — 2013-09-07T20:24:28Z
First step yes, but I have some questions (don't take this too seriously though):
- Is WinRT viable, or is it just going to fade away and die? It seems to me it's less exciting than Silverlight, which is on life support. It's no big deal if people want to add support to D (hey, it's their free time spent on it, not mine), but it seems like an almost dead platform to me..
- Does Windows accept apps built with D for WinRT? AFAIK they all have to go through the Windows store, which means MS has to approve them, right? I really have no clue, I know Apple used to ban other languages (remember that huge backslash story, heh).
Comment #2 by flyboynw — 2013-09-09T11:34:35Z
For the most part, WinRT is an OO wrapper around Win32. But it's probably better to think of it as Microsoft's new method of developing API's for Windows. For example, if you want any of the new Sensors API's your ONLY option is WinRT. Practically, Win32 has been deprecated for new work.
Silverlight was DevDiv, and was a major threat to WinDiv because it allowed you to develop on OSX. Internal politics put SL on life-support. :-)
Unlike Apple, the Windows Store makes no specification about the language used to construct apps. The acceptance process consists of a gamut of automated and IRL-user performance and standards conformance tests.
Comment #3 by andrej.mitrovich — 2013-09-09T12:32:23Z
(In reply to comment #2)
> For the most part, WinRT is an OO wrapper around Win32. But it's probably
> better to think of it as Microsoft's new method of developing API's for
> Windows. For example, if you want any of the new Sensors API's your ONLY option
> is WinRT. Practically, Win32 has been deprecated for new work.
Hmm yeah, from what I hear win32 is still being used behind-the-scenes for WinRT, which probably means it won't go away any time soon. I think the "start menu" backslash and subsequent reintroduction shows MS can't really break features without paying a price. I mean, imagine if win32-based apps didn't work in e.g. Win9, I think that would make it a dead-on-arrival OS.
Well, I reserve my doubts about WinRT, but if someone wants to work on it, go ahead.
Comment #4 by robert.schadek — 2024-12-13T18:11:18Z