Discussions

I find the LINQ syntax easier to comprehend than the extension method syntax:

var data =
    from item in list
    group item by item.Key into gruppe
    from item in gruppe
    orderby gruppe.Key, item.Value
    select item; 

Technically, you don't need to group them:

var data =
    from item in list
    orderby item.Key, item.Value
    select item;

5 days ago, spivonious wrote

@PerfectPhase: And just so you know, the "select item" part isn't needed.

That isn't correct.  I get a "query body must end with a select clause or a group clause" error without it.

I use USB keyboards and mice all the time.  Not sure why you think it is just for hard drives.

As for bandwidth, wireless Bluetooth can handle HID fine so I'm sure wired USB can too.

Anyways, the UI latency you've noticed is likely caused by application-level latency, not hardware-level or driver-level latency.  It's easy to see this if you play a game with light system requirements.

@W3bbo: Never say never. Sometimes there are bugs that are specific to browser versions.

Others: Use "msSiteModeCreateJumplist" in window.external instead.

It would be nice if Microsoft could just drop Win32 and adopt a Web-based UI API for some new version of Windows, but being able to run legacy Windows applications is something Microsoft cannot sacrifice to make that happen.

IBM had a similar dilemma with mainframe applications, and even though mainframe applications are not sexy or innovative, they're still making money for IBM and others involved in the care and maintenance of such software.

20 years from now, Google may have the same dilemma with Web applications when the "next big thing" displaces them.

There's overhead to setting up asynchronous code to execute so you should analyze your performance and scaleability bottlenecks before you implement such code.  The new async/await syntax mitigates the readability/maintainability tradeoff for implementing asynchronous code, which is great.

I'm looking forward to Beta 2 (if there's going to be one).  I encountered stability issues and minor layout bugs with Beta 1.

I appreciate the strategic shift in focus for Silverlight.  Focus on making Silverlight a great platform for Windows Phone development, and let HTML 5 shine for Web development.

They usually do Silverlight releases at MIX, not PDC.

I really like the new async/await syntax.  It makes a lot of sense if you do a lot of asynchronous programming and have come to hate callbacks and having to roll your own exception handling recovery and cancellation mechanisms.