Linked by twitterfire on Mon 24th Oct 2011 22:52 UTC
Thread beginning with comment 494290
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
Features
Linked by Thom Holwerda on 05/21/13 21:38 UTC
Linked by Thom Holwerda on 05/20/13 11:29 UTC
Linked by Thom Holwerda on 05/18/13 21:33 UTC
Linked by David Adams on 05/16/13 4:23 UTC
Linked by Thom Holwerda on 05/11/13 21:41 UTC
Linked by Thom Holwerda on 05/08/13 14:22 UTC
Linked by Thom Holwerda on 05/02/13 15:28 UTC
Linked by Thom Holwerda on 04/29/13 21:06 UTC
Linked by Thom Holwerda on 04/24/13 22:24 UTC
Linked by Thom Holwerda on 04/18/13 11:21 UTC
More Features »
Sponsored Links



Member since:
2005-11-29
WinRT looks to be what CLR was supposed to be, pushed lower level to support serious C++ right (read COM 2). CLR on the other hand is left as a high level application dev wrapper/runtime for ever. Looks like dreams of managed only OS'es will remain pipe forever.
I think so, but I agree with this decision because it avoids code duplication. For example, they'll write a great UI platform (WPF, or Silverlight) but then C++ and other langguages are out in the cold.
With WinRT, they ported XAML and all the graphics stack to C++ and exposed them as WinRT components, so C++ benefits from this awesome UI framework too.
The equality amonst the languages is what I love the most, and its why, even though I'm generally a hard ass, I'm willing to admit this is a better approach.
Previously they had an all-or-nothing thing going on, this is a little more encompassing. We're all Metro developers now.