The literature touts quite a lot of benefits of using the MVC pattern, which to me are really the benefits of designing by separation of concerns. I want to know whether there are any scenarios when it would be detrimental to use MVC or separation of concerns in designing a system or application.
posted 7 years ago
Separation of concerns is truly the first step towards maintainibility, extensibility, scalability - so I dont see any place where you wont need separation.
when it would be detrimental to use MVC or separation of concerns in designing a system or application.
When a view model and controller are not used ? MVC applies to various frameworks like Struts, Swing etc. It would not make sense for example to use MVC for a javaMail API (Assuming the APIs responsibility to ONLY to send emails)