Shouldn't MVC be MCV?

Question

The model is defined first, then the controllers are fired based on the user request, and they will generate the views (the output).

So it should be M->C->V, right?

Agreed, I've always found this a little puzzling when I first heard about MVC. — Kevin Wang, Feb 26 '12 at 00:38
maybe it's in order of importance: Model is the most important, View is how the end-user sees the model and Controller just binds the 2 toghether — ratchet freak, Feb 26 '12 at 00:48

score 7 · Answer 1 · answered Feb 26 '12 at 01:24

7

Because that's how the originator of the term ordered it.

"MVC was first described in 1979[3] by Trygve Reenskaug, then working on Smalltalk at Xerox PARC."

http://en.wikipedia.org/wiki/Model%E2%80%93view%E2%80%93controller

answered Feb 26 '12 at 01:24

steve_sch

266

score 4 · Answer 2 · answered Feb 26 '12 at 00:39

4

Maybe it comes down to dependancies and usage? Each item on the right knows about or uses the item on the left. Controller knows about views and models. Views know about Models. Models just know about themselves. So hence the naming convention MVC. Just my thoughts.

answered Feb 26 '12 at 00:39

dreza

3,476

3

It could also be, you know, just because. – Kevin Wang Feb 26 '12 at 00:42
@KevinWang "Ours is not to question why. Ours is but to do and try"... – dreza Feb 26 '12 at 00:55

TheTechGuy · Answer 3 · 2012-02-26T02:38:38.937

2

Yes this should be MCV but many acronyms are made in wrong order just because they sound better that way.

AmVeeSee  (more fluent) 
AmSeeVee  (less fluent)

edited Feb 26 '12 at 02:38

answered Feb 26 '12 at 01:23

TheTechGuy

1,045

Shouldn't MVC be MCV?

3 Answers3