I can see your point and certainly I've seen code as you have described. However, just because the model lives on a server doesn't mean that you can't have a mo

I can see your point and certainly I've seen code as you have described. However, just because the model lives on a server doesn't mean that you can't have a model class on the client. If that were true, then we would not be able to have model classes tied to databases. But that's fairly common, even if it does add a level of abstraction. The big mistake that folks make is not that they use MVC on the client but that they use MVC on the server side in this scenario. You'd get better bang for your buck if you used MVC on the client and accessed RESTful resources via a model class, and treated the server like a filesystem for loading controller and view classes that were handled exclusively by the client.