Question

Shouldn’t models just describe data that will be passed from a controller to a view? Doesn’t that make models unnecessary in weakly typed languages? In PHP, they are doing DB work in models, but isn’t that wrong? As I see it, models are just unnecessary in weakly typed languages…

Answer 1

There are some misconceptions about the term model. Microsoft’s MVC3 framework has the concept of a view-model, which is simply the data you use to render your views. This isn’t however what the M stands for exactly in MVC. The model includes your business entities. We have thin controllers and fat models, but very thin view models. Our controllers make calls to services that perform business logic, and the controllers never do this logic themselves. We then translate our business entities (our data models) and convert them into a lightweight view model, which can be used for rendering a view.

So to answer your question

Shouldn’t model just describe data that will be passed from controller to view?

Then perhaps what you are really asking is aren’t view-models unnecessary? I’m not sure why you think this. View model + view makes the result. In PHP it can be helpful to define a class with easily accessible properties on it. This is just sensible for clarifying your expectations and prevents you from calling methods with hideously long sets or arguments. In JavaScript there is no need to define a view model as such, you just push the properties onto a new object and pass it along with your view to your view rendering logic. This is more a reflection of the OO pattern these languages use and not the fact that they are weakly typed.

If you are asking if model is unnecessary, then you have missed the purpose of the MVC architecture. A big part of MVC is that you separate your concerns. Why apply any architecture to your code? I am sure you can find a better explanation of the motivation behind MVC than I can give you.