MVC Pattern Debates
This cluster revolves around debates on the definition, implementation, and criticisms of the MVC (Model-View-Controller) architectural pattern, including its separation of concerns, comparisons to frameworks like Rails and React, and historical origins.
Activity Over Time
Top Contributors
Keywords
Sample Comments
WTF? It's very different from MVC.
None of my articles points at issues with "regular MVC"
This is the essence of MVC/MVP architecture!
Well, "things like react" are not more than the V in your MVC ;)
Doesn't this go against the MVC grain -- UI / model separation of concerns?
Yes there is, model and view are dumb roles which makes controller do everything under the sun
MVC is just a design pattern, a way to organize code, it's not a religion.
Many people accept the MVC dogma as the word of god. In truth, it is a design trade-off just like anything else. You should really look at SeaSide or UncommonWeb. In SeaSide the view and controller are combined into a component in the way you describe as intuitive. In Rails best practice is to create partials (partial views) that can be re-used across views, put code into the model instead of the controller, and use before_filter to trigger re-usable functions.
You're overfitting to your knowledge of MVC.
You're gonna have to provide a bit more context for that. What part of the MVC pattern?