While I appreciate the fact that many "traditional" MVC frameworks fall down when it comes to threading, events, long running connections, event handling, actor

While I appreciate the fact that many "traditional" MVC frameworks fall down when it comes to threading, events, long running connections, event handling, actor-based concurrency, asynchronous processing, and multiple data / presentation resources ... I don't think MVC is the root of the problem. In fact, MVC doesn't really have anything to do with those issues: it is a pattern addressing the separation of concerns, whereas the shortcomings in the article relate to specific implementation of frameworks that also happen to follow the MVC pattern. That said, there certainly is a new direction emerging for web applications: we're entering the world of sophisticated software. :)