News for hackers. Stuff that matters.
Re:MVC is dead, it's time to MOVE on by rorrr on Monday July 02, 2012 @01:52PM (#4189939)
So you renamed "controllers" to "operations".
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?
Re:MVC is dead, it's time to MOVE on by divtxt on Monday July 02, 2012 @02:14PM (#4190068)
And callback "events" have been renamed to... "events".

I'm going to have to agree with the parent here. Without example code to compare, how is this different than MVC? (or "MVCE")

Re:MVC is dead, it's time to MOVE on by 1qaz2wsx3edc on Monday July 02, 2012 @02:13PM (#4190066)
Yah, this reminds me of Ember.js "MVC". It's kind of like "MOVE" + a StateMachine.

http://emberjs.com/images/ember_mvc/embermvc.png

Operations are similar to controllers for sure. But where's routing or state? We don't have a full picture here.

After trying out that new meta-pattern, things get overly coupled, too many bi-directional relationships between state, views, models, and controllers/operations.

Re:MVC is dead, it's time to MOVE on by dclowd9901 on Monday July 02, 2012 @02:16PM (#4190081)
And am I incorrect in seeing it as simply MVC with an events bus? Welcome to everything backbone.js already brought to the table.
Re:MVC is dead, it's time to MOVE on by drone on Monday July 02, 2012 @05:45PM (#4191195)
... I'm pretty sure typical MVC uses some form of event as well, i.e. an event is created to inform the view that the model has changed. (Even the wikipedia page differentiates passive MVC implementations where the language/platform cannot implement events.)

Somehow, I'm just seeing the Observer pattern and the MVC pattern in the OPs post.

Re:MVC is dead, it's time to MOVE on by sic1 on Monday July 02, 2012 @03:10PM (#4190400)
My thoughts exactly. Extend your main app var with Backbone.Events and u have a global event system.

app.trigger 'boom'

Re:MVC is dead, it's time to MOVE on by trebor on Monday July 02, 2012 @02:03PM (#4190011)
No. An operation appears to be a one-off "action" rather than a collection of actions (like a controller).
Re:MVC is dead, it's time to MOVE on by alttab on Monday July 02, 2012 @02:05PM (#4190022)
This is a small difference. You can say that an operation is simply a controller with one method in it.
Re:MVC is dead, it's time to MOVE on by bradwestness on Monday July 02, 2012 @02:44PM (#4190248)
So basically he's just putting the controller methods in their own namespace. Which is all well and good, but I don't think anybody argues that all of your business logic has to be in the controller class for it to be considered MVC.