is MVC dead?, time to MOVE on

First of all, I want to clarify that in this context MVC means architectural pattern (http://en.wikipedia.org/wiki/Model%E2%80%93view%E2%80%93controller[^]) and not the ASP.NET framework using this pattern (http://www.asp.net/mvc[^]).

I would use a lot of caution with the claim written in pure advertizement style. And the whole idea to praise MVC, even with exaggeration, and then deny it on based on the shear statement "it's designed with decades old technologies" looks purely dumb.

Actually, so far, I did not find anything clearly explained the pattern, only few links just referencing or copying the same short article, advertizement claim and picture. I won't be much surprised if it turns out that this is merely a… hoax. I just don't know.

The things are more serious than that. I cannot deny that MVC may go out of circulation eventually. The absurdity of this article is playing with the idea that MVC is something like a dominating paradigm, a state in development of technology, which can be replaced with something more advanced. This view is pure manipulation. In fact, there is a number of alternatives of the patterns of this type: MVA, MVP, MVVM… The speculations on the fact that MVC is discussed the most (MVVM can also be named as popular these days) cannot be used as an argument that one pattern is superior or inferior to others. It's all about claims and gossips, nothing about logic and rationality, something like ten millions users cannot be wrong (oh, they can!)…

But things are even more serious. I wrote many times to warm against taking patterns too seriously. Too many developers make the idea of using the "best patterns" more important than the the goals of their own projects, as if the goal of the project was to implement some pattern ("me too"). This is wrong. The patterns (design patterns or architectural, it does not matter) are not just used. Architectures are created for the project, design decisions are made. Then people think about solving some archetypical problem found in their development on more universal level, perhaps putting then in a distinct layer of the project architecture. At this moment, it's good to look around and think "what if other people already did something similar and applicable to my project, too?" And this is where the patterns can help.

Being proud of using the most modern and trendy patterns is just silly. Imagine you have no information on some project except the fact that it uses some very modern patterns; what would you say? My first idea would be: "it may mean that the project is nothing special at all, it does routine thing, as very many projects of this sort". And this is more or less normal and understandable. The simple understanding that patterns are formulated and published to help people developed projects (architectures, in case of MVC), and not that projects are developed to implement patterns, should make understanding of the absurdity of such "MVC is dead" arguments pretty clear.

—SA