meh. Doesn't address any of the actual issues with writing an MVC web application. MVC -> Views are templates, Controllers are HTTP server end point bindings

meh. Doesn't address any of the actual issues with writing an MVC web application. MVC -> Views are templates, Controllers are HTTP server end point bindings and Model is everything else. Rookie mistake; put logic in controller actions. No! This is a terrible idea: your controller should never do more than: parse input, apply update to some model object, generate response view model. 'Model' does not mean 'Something that serializes and goes into a database'. It means everything else. The entire state and associated classes that manipulate that state. That's where these operations from MOVE exist. I mean, if you want to critize MVC (especially some popular frameworks...), go for it, but I'd be much more interested to hear how a new approach addresses: - What about all that javascript / flash / etc? Where does that fit in? - How do you effectively test controllers and views?