WinRT demystified
tirania.org
WinRT demystified
1–10 of 48 posts
Re: WinRT demystified
#2Asynchronous API that will really make a difference for the end user, right? There won't be any more waiting for UI to unfreeze :)
Re: WinRT demystified
#3Re: WinRT demystified
#4 When you use C# and VB, you are using the full .NET
framework. But they have chosen to expose a smaller
subset of the API to developers to push the new vision
for Windows 8.
For me, this is a really interesting point that this article doesn't fully get. When you use WinRT you might be using the C# compiler, CLR runtime and .NET string & collection classes, but there are huge sections of the .NET BCL that now look like a lame duck. WinRT is the new way to do XML, JSON, HTTP, networking, security, globalisation, threading, printing... (more here: http://msdn.microsoft.com/en-us/library/windows/apps/br21137...)You can still use the full .NET class library when doing ASP.NET, but who wants to use different JSON classes for App development vs. Web development? Won't the WinRT version gradually become the preferred way of doing JSON in both environments, with the .NET BCL existing to fill in the server side only gaps?
Re: WinRT demystified
#5Re: WinRT demystified
#6It's amazing to see just how much Apple is driving the industry. Microsoft is making an app store, completely rethought their UI and programming model for mobile devices...
Re: WinRT demystified
#7It's amazing to see just how much Apple is driving the industry. Microsoft is making an app store, completely rethought their UI and programming model for mobile devices...
Re: WinRT demystified
#8It's amazing to see just how much Apple is driving the industry. Microsoft is making an app store, completely rethought their UI and programming model for mobile devices...
Um, it sounds like 'mobile' is driving the industry. Apple is a player too, just like everybody else.