Not just for the user - calling asynchronous tasks using the new C# or VB keywords is so mind-bogglingly easy that you'll just have no excuse not to do it when writing apps.
Even the use cases that are not covered by the two keywords, like fetching a whole bunch of stuff together or issuing a lot of requests and having the data trickle in as they are completed one by one are handled easily with the Task API, to the point where you have WhenAny and WhenAll methods and you just do "await Task.WhenAll(tasks)".
I agree. This API will be a paradigm change for Microsoft. I particularly liked Miguel's explanation as well. In fact, it's the only one I found that really explained it in programmer's terms. Now, how soon will there be a Mono implementation fo this I wonder?
Asynchronous API that will really make a difference for the end user, right? There won't be any more waiting for UI to unfreeze :)