WinDiv promised a 'fast and fluid' way to close metro apps in the beta.
I has some problems with the start screen and task switching, too, not 'terrible' but 'annoying', I will try again for the beta.
Hmm... so, let me check some recent interesting MSR papers
Code Space: Combining Touch, Devices, and Skeletal Tracking to Support Developer Meetings
Kinect for Coders, finally...... oh not for coding, yet.
What is a File?
many lessons learn from WinFS ..... and many other stuff
PTask: Operating System Abstractions To Manage GPUs as Compute Devices
GPGPU for OS kernel...... sounds like something Midori team should be interested
Two for the Price of One: A Model for Parallel and Incremental Computation
updates from Daan leijen and Concurrent Revisions....."When repeating the computation after a small change, the speedup is much beyond the reach of optimal parallelization (8x), rang-ing from 12x to 37x." sounds interesting.
My main concern on the managed compiler is the performance, you know, like Herb and Charles said, if you want reeealy good raw performance, you should go native, and compiling is really a performance critical task, how does the 'Going Managed' work ??
as Eric Lippert said 'the performance of the entire analysis engine is not as high as we would like ', so what are the pain points and what's the plan to get the performance back ? do they need some really unatual dirty tricks like people do in XNA stuff ? what's the difference in performance characeristics of the native and managed compilers ? like 'which one is good at what' stuff.
actually Eric has answered many questions in the comment of his post, he is in good communications.
I feel like Roslyn is the 'Kinect SDK' in some sense, I would expect some magical 'cool hacks' from it.
Somasegar seem to have published a post today "Roslyn CTP now Available", but apparently it got deleted.
I guess its not 'deleted', just being hold back for some internal reviews kinda stuff, should be published VERY SOON.
OK, let me try to clarify the situation a little bit.
First, there was Avalon, implemented on CLR, its called WPF.
Then, there was agcore (Avalon Graphics core), implemented in native code, but exposed by CoreCLR, its called WPF/Everywhere or Silverlight.
Somewhere, they exposed agcore by compact version of CLR, its called Silverlight for Windows Phone.
now, there is Windows.UI.Xaml, implementation directly derived from agcore, but exposed by Windows Runtime, its called XAML, or WinRT UI, or Jupiter I believe.
so, Avalon lives on, but CoreCLR is lost.
No. This is the platform-specific 'Silverlight' as a native client application development framework. This kind of 'Silverlight' is living for sure, as in 'Silverlight for Windows Phone', or even 'Windows Runtime'.
It was the 'cross-platform RIA web app framework' called 'Silverlight' that we think is dead. still no evidence to deny this.
I guess a better wording could be 'CoreCLR is dead'. And I guess even 'Silverlight for XBox' runs on the full CLR.