3 ms·
There is MVC. Its just a concept, unlike those design patterns from GoF which are specific. Models are just data, View are just representations and Controllers
by fadzlan 14y ago
There is MVC. Its just a concept, unlike those design patterns from GoF which are specific.
Models are just data, View are just representations and Controllers are just endpoints. You can program your own way in your language, and if you can categorize your code as such, you can argue it is MVC.
And of course, because its just a concept, anyone in the world can argue why your implementation is not MVC as well.
No, MVC is not the reason to justify Spring, inversion of control, containers, dependency injection, annotation and all other "enterprisey J2EE-esque shovelware" as you mentioned.
MVC has been around since SmallTalk (you know, before even Java...). Heck, you even get MVC in Rails. You see Spring in Rails? Dependency Injections? Annotations? Of course not, since I could not even begin to think they are related.
- specialist 14y agoOf course not, since I could not even begin to think [Rails and Spring] are related. Sure they are. Spring is the Java community's effort to get some of that dynamic programming goodness (ahem). Rails is the Ruby community's effort to reproduce the unmaintainable mess of J2EE. You couldn't have one without the other.