是MVC死了吗？，时间到了 [英] is MVC dead?, time to MOVE on

问题描述

您好，



我使用asp.net网络表单创建了网站。但现在要建立一个响应和其他功能的网站。我正在考虑使用MVC5和EF 6.1.1创建项目，因为我有visual studio premium 2013 update 3许可版本。



但是当我搜索MVC时，一个参考https://cirw.in/blog/time-to-move-on说MVC已经死了。时间到了MOVE上。



MVC6也来了。如果MVC不是死的意思，使用MVC6或MVC 5创建网站是否合适。所以请以正确的方式引导并建议我。



需要帮助。

Hello,

I created website using asp.net web form. But now to make a website to be responsive and for other features .I am thinking to create project using MVC5 and EF 6.1.1 as i have visual studio premium 2013 update 3 licensed version.

But when i search about MVC, one reference https://cirw.in/blog/time-to-move-on says that MVC is dead.time to MOVE on.

MVC6 also has come. if MVC is not dead means, is it good to create website using MVC6 or MVC 5.so please lead and suggest me in correct way..

help needed.

推荐答案

首先，我想澄清一下，在这种情况下，MVC意味着架构模式（ http://en.wikipedia.org/wiki/Model%E2%80%93view%E2%80%93controller [ ^ ]）而不是使用此模式的ASP.NET框架（ http://www.asp.net/mvc [ ^ ]）。



对于以纯广告风格撰写的声明，我会非常谨慎。并且夸大MVC的整个想法，即使夸大其词，然后基于剪切声明它是用几十年前的技术设计否认它看起来纯粹是愚蠢的。



实际上，到目前为止，我没有找到任何清楚解释的模式，只有少数链接只是引用或复制相同的短文，广告声明和图片。如果事实证明这仅仅是一个骗局，我不会感到惊讶。我只是不知道。



事情比这更重要。我不能否认MVC最终可能会失去流通。这篇文章的荒谬之处在于，MVC就像一个支配范式，一个技术发展的国家，可以被更先进的东西取代。这种观点纯属操纵。事实上，这种类型的模式有很多种选择：MVA，MVP，MVVM ......关于MVC被讨论最多的事实的猜测（MVVM现在也可以命名为流行）不能用作参数一种模式优于其他模式。这些都是关于声称和流言蜚语，没有关于逻辑和理性的东西，千万用户不可能出错（哦，他们可以！）......



但事情还是更多严重。我写了很多次来反对过分认真对待模式。太多的开发人员认为使用最佳模式的想法比他们自己项目的目标更重要，好像项目的目标是实现一些模式（我也是）。这是错的。不仅仅使用模式（设计模式或建筑，无关紧要）。为项目创建架构，制定设计决策。然后人们考虑在更普遍的层面上解决他们的发展中发现的一些原型问题，或许把它放在项目架构的一个独特层面。在这个时刻，环顾四周并思考如果其他人已经做了类似的事情并且也适用于我的项目会怎么样？这就是模式可以提供帮助的地方。



以使用最现代和时尚的模式为荣，这简直是愚蠢的。想象一下，除了使用一些非常现代的模式之外，你没有关于某个项目的信息。你打算说什么？我的第一个想法是：它可能意味着项目没有什么特别之处，它只是常规的事情，因为这类项目非常多。这或多或少是正常的，也是可以理解的。简单理解模式的制定和发布是为了帮助人们开发项目（体系结构，在MVC的情况下），而不是开发实现模式的项目，应该让人们理解这种MVC已死的荒谬论点非常清楚。

-SA

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

这篇关于是MVC死了吗？，时间到了的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！