If this was true, what kind of metadata and/or code would be required to implement Controllers to solve the majority of use cases? . . .
For most applications, a major goal for developers is to program in a language that is relatively comprehensible to the client who has to specify the requirements. If you're coding for loops and they're talking insurance coverage rules, that mismatch will typically make both specifying and maintaining the code more difficult than it needs to be. This is one of the big drivers of Domain Specific Languages - allowing programmers to write solutions that (at least at a high level) are described in terms of the problem domain.
One of the big trends in ColdFusion frameworks has been the move from a page controller model to a front controller. In this posting I am going to argue that for many use cases this is not a great choice.
While continuations are by definition a function of languages that use closures, the same basic approach could be mimicked in CF by simply storing a modest set of information in session state.
I am not convinced that continuations are the one true way to write web apps, but I think it is time to get beyond a simple stateless event=xxx paradigm and to talk about more interesting approaches . . .
What is everyone else doing?!