Why is MVC so popular?

Question

I was originally going to make this a longer question, but I feel like the shorter I make it, the better you'll understand what I mean.

• The MVC architectural pattern has 3 dependencies. The View depends on the model. The Controller depends on the View and Model. The Model is independent.

• The Layers architectural pattern defines N - 1 dependencies, where N is the number of Layers.

Given three Layers: Model, View, and Controller, there are only 2 dependencies, as opposed to 3 with traditional MVC. The structure looks like this:

View ---> Controller ---> Model

[View depends on Controller, Controller depends on Model]

It seems to me that this style accomplishes the same goals and produces looser coupling. Why isn't this style more common? Does it truly accomplish the same goals?

Edit: Not ASP.NET MVC, just the pattern.

With regard to griegs's post:

• As far as mocking, Layers still allows you to use the Command Processor pattern to simulate button clicks, as well as any other range of events.
• UI changes are still very easy, perhaps even easier. In MVC, the Controller and View tend to mesh together. Layers creates a strict separation. Both Layers are black boxes, free to vary independently in implementation.
• The Controller has 0 dependencies on the View. The View can be written, and time can still be saved with loose coupling.

Answer 1

I'd like to add some more things. First of all for my point of view is we use the model as container for the information we want to pass and show on the view. Usually the action method into the controller ends with return view("viewName",model).The view itself probabily will change its layour against the model :

on the view :

if(model.something==true) {

%>

somethign to show

<%

}

At this poinf the definition of model is hard to find.

I can say (especially on enterprise conext) the are two "model"

one is the domain model/entity model or how you want to call it that wraps the data coming from the lower layers (database,etc) and the view-model who contain the information we wants to show plus any other information we need to hide/show portion of interface

The controller orchestrate the the views and is indipendent from the view but a bit dipendent from the model:

into the controller

pulic actionResult Index(){

....

if(model.BoolProperty==true){

return ("firstView);

}

else

{

return ("secondView");

}

}

I hope it makes sense

Answer 2

Because you decouple the interface from the controller making changes easier.

Also consider the scenario where you need to get started on a project but the artwork won't be ready for weeks or months. Do you wait or do you write all the code required for the pages and simply then wire up the view to the controller.

At least that's what we did and we saved months.

Also it made UI changes easier to cope with because there wasn't any code in our aspx pages that did anything.

Our tests were also better as we could mock up anything including button clicks etc.

And if you're talking about the asp.net-mvc framework, there is no code in the aspx files and no viewstate etc.