News for hackers. Stuff that matters.
Re:MVC is dead, it's time to MOVE on by pestaa on Monday July 02, 2012 @02:05PM (#4190026)
It splits controllers into operations and events.

Out of the three terminologies (state, representation, flow), the third one is arguably the most tangled. I find it healthy to refactor it into reusable chunks (operations) and event-driven flow management.

The problem was, in my opinion, that operations should have not been put into controller units. It attracted more copy-paste solutions in my experience.

Re:MVC is dead, it's time to MOVE on by cbsmith on Monday July 02, 2012 @09:06PM (#4191931)
> It splits controllers into operations and events.

The original MVC designs and sample code all had views and controllers observing models through an Observer based event pattern.

The operations were the controller units. The events were not.

Re:MVC is dead, it's time to MOVE on by utilitron on Monday July 02, 2012 @02:32PM (#4190178)
What is the difference between that and adding a service layer to a MVC?
Re:MVC is dead, it's time to MOVE on by rcgs on Monday July 02, 2012 @02:42PM (#4190234)
There isn't, but then is MVC really MVC when you've added in another layer?