[Warning this post may jump around a bit... ]
I was reading Rick Strahl's assessment of "What's Ailing ASP.NET Web Forms?" Rick ends with the idea that MVC is probably not the answer although it solves an issue that we have at the moment. He mentions that maybe MS should invest some time into creating a new Web Framework. I was right there with him.
From there I moved over to looking into the new PLINQ stuff. That's Parallel LINQ. This got me thinking that our code isn't necessarily written for modern day (multi-core) processors.
Our machines simply can do multiple things at once (at least that's how I understand it). I read an article about a year ago that talked about how we need to start considering that when we write single threaded apps we are not taking full advantage of the processor.
I'm sure things like the Windows Forms Event model takes advantage (somewhat) in parallel processing.
Regardless if it does or not I've been thinking about what an app look like that took advantage of multi-core's ability to process multiple threads at once (if that's possible).
I can envision something MVC like. Where the main thread kicks off the data process (which might in turn kick off additional threads) where entities are built and then dropped off into some common area (I know my terms are all wrong) where the main thread simply waits to pick up the data and display it.
Saves would happen in a similar manner in that data would be handed off to the data processing thread and a complete, or error is the result.
Anyway, I'm talking about stuff that I'm not that well-versed in, but I can dream some interesting app frameworks that would be multi-threaded at their core. Although I'm not sure how useful something like this would be for web frameworks...
I'll admit I like ASP.NET even though I have encountered my share of warts with it... MVC still seems like a lot more work for minimal bang for my buck... although I can see it's usefulness in complex apps.