3 ms·
I was never a fan of "strict" web MVC. It felt like you were jamming far too much into your models. Take Symfony2's architecture, for example. Controllers, Ent
by jtreminio 13y ago
I was never a fan of "strict" web MVC. It felt like you were jamming far too much into your models.
Take Symfony2's architecture, for example. Controllers, Entities, Repositories, Views, Services, Listeners, Events, etc. Each layer has its own distinct purpose that do something very specific by themselves, but when brought together form a very cohesive whole.
- deleted 13y ago[deleted]
- dscrd 13y ago>Take Symfony2's architecture, for example. Controllers, Entities, Repositories, Views, Services, Listeners, Events, etc. Each layer has its own distinct purpose that do something very specific by themselves, but when brought together form a very cohesive whole. But the end result is so very complex and the benefits gained are doubtful at best.
- camus 13y agoYou obviously never worked with javaEE ... Symfony is a breeze compared to how the former works.