Inside Windows 8: Martyn Lovell and Elliot H Omiya - The Windows Runtime
- Posted: Nov 12, 2012 at 12:54 PM
- 54,059 Views
- 9 Comments
Loading User Information from Channel 9
Something went wrong getting user information from Channel 9
Loading User Information from MSDN
Something went wrong getting user information from MSDN
Loading Visual Studio Achievements
Something went wrong getting the Visual Studio Achievements
Right click “Save as…”
Windows 8 introduces an application programming model for building new kinds of user mode apps called Windows Store Apps. The name reflects the new way users discover, download, purchase, rate, and install applications on Windows 8: The Windows Store.
On Windows 8, underneath this new application model is the Windows Runtime (WinRT for short), which provides an API and ABI as well as services for these modern Windows applications. WinRT is a security sandbox and an advanced execution environment. It enables efficient interoperation among very different language "projections"—so, JavaScript, for example, can seamlessly interact with C++.
What is WinRT, exactly? Why is it designed the way it is? What's the history of WinRT? What are the primary goals of this new technology? How did the Windows engineering team arrive at the design and implementation of this new Windows user mode development platform? These are the key questions addressed in this conversation with Windows Runtime engineering leaders Martyn Lovell and Elliot H Omiya (we call him EHO). Elliot and Martyn are two of the original WinRT architects. Watch as they tell us how it was conceived, how it works, and why COM is such a big part of the equation (it's not your grandmother's COM, mind you. WinRT is a very different COM than classic COM).
Huge thanks to Martyn and EHO for this excellent conversation.
Tune in.
Comments have been closed since this content was published more than 30 days ago, but if you'd like to continue the conversation,
please create a new thread in our Forums,
or
Contact Us and let us know.
Follow the Discussion
Oops, something didn't work.
What does this mean?
Following an item on Channel 9 allows you to watch for new content and comments that you are interested in. You need to be signed in to Channel 9 to use this feature.What does this mean?
Following an item on Channel 9 allows you to watch for new content and comments that you are interested in and view them all on your notifications page.sign up for email notifications?
It really does work the way they describe it, extraordinary!
Ah, good stuff. I'd really like to see a good deal more drill downs into WinRT.
@dot_tom: You will
The next in this series is a very deep conversation with whiteboarding covering the new app model. It's the next Going Deep episode.
This one was a historical and architectural overview, introductory in nature. It also included some information that's most likely new to you.
C
NICE.
I requested this series in 2011, apparently
http://channel9.msdn.com/Shows/C9-GoingNative/GoingNative-1-VC-vNext-CRT-C-and-Beyond#c634499607690000000
@felix9: Such is timing.
C
"For better or for worse, desktop apps are desktop apps." -- this quote makes me sad. It says to me that no investment has been made to improve the desktop developer's life. As a scientific data visualization tool, our app has MANY windows (and needs all of them). We would LOVE to do XAML UI in C++ with our desktop app. A Windows Store app makes no sense at all for our app. What do we desktop devs have to look forward to? We use WPF now (from C++/CLI) but it's just too darn slow and uses .NET but only so that we can use WPF + XAML.
I would be disappointed if Windows 9 did not do something for the desktop now that the tablet UI is a done deal. But it's understandable that they couldn't overhaul the desktop as well in the same timeframe.
Great video. Enjoyed it a lot. WRT is a really great story for developers.
I feel similarly. We have legacy dependencies which won't pass the restricted WinRT API. Here's hoping that we'll get language projections and native XAML for desktop use (or side-loaded enterprise apps which can be compiled with fewer restrictions).
From what I'm seeing from Build, it seems they are catering to the HTML/js devs while abandoning the c# devs
Remove this comment
Remove this thread
close