Published: Jul 03 2012 / 01:11
Not for me, Still lots to do with MVC.
I'm definitely one of those people who stuff everything into a controller, because (a) I feel the logic doesn't belong in either a model or view or (b) I just dont know where else to put it.
Read this piece earlier today, and it's got my gears turning.
How can MVC be dead? Just because the author does not like it? Just because it is old does not mean it is outdated. Practically in every platform and language, there are numerous active MVC frameworks for desktop. mobile and web applications and those are not going to go away soon. Stuffing a lot of code into the controllers is definitely not a good idea. You should refactor those code into into different class or utilities and call them from the controllers. It is as simple as that. MVC has certain variations and MVVM is one of them which the author should consider.
MVC vs MOVE (model, operation, view, event). Basically he's implementing controllers as operations & events. That sounds fine, but why is MVC dead then? All you did was say C=EO and shuffle the letters.
Html tags not supported. Reply is editable for 5 minutes. Use [code lang="java|ruby|sql|css|xml"][/code] to post code snippets.