4 ms·
Yeah, MVC (and MVVM for that matter), seem like architectural approaches that are great in theory, but with the reality of constraints, requirements, timelines,
by sky2224 2y ago
Yeah, MVC (and MVVM for that matter), seem like architectural approaches that are great in theory, but with the reality of constraints, requirements, timelines, and ultimately many engineers' misunderstanding of things (frankly I'm probably included in that group as well), it just leads to a mess of interdependency and tight coupling among functionalities.
Now granted, this is pretty much a given for any architecture (nothing is perfect): so maybe my expectations of what things should be needs to be reeled in a bit.
- breadwinner 2y ago> it just leads to a mess of interdependency and tight coupling among functionalities Disagree with that. Most UI frameworks, including ASP.NET Core, JSP and JSF (Java based frameworks), Ruby on Rails, and Django (Python) are all based on MVC. That's no accident. MVC works very well.
- sky2224 2y agoReally? I'll admit most my experience has first been in an ASP.NET 4.x environment and currently in WPF MVVM. It's been a mess. Maybe I've just had bad luck seeing these architectures in action?