>But in my follow up, I was basically asking if, from the perspective of the view, it makes much of a difference if it's communicating with a Backbone model or a Redux store.
I think it makes a difference. When you work with a Backbone model, you directly modify it:
model.set('completed', true);
When the logic changes, you need to change the call sites to call a model method or several model methods.
On the other hand, with Redux the view specifies what it wants to happen and not how:
dispatch({ type: 'TOGGLE_TODO', id })
When you need to change how the whole state tree responds to that change you don’t need to change the components. This is the difference.
I think it makes a difference. When you work with a Backbone model, you directly modify it:
When the logic changes, you need to change the call sites to call a model method or several model methods.On the other hand, with Redux the view specifies what it wants to happen and not how:
When you need to change how the whole state tree responds to that change you don’t need to change the components. This is the difference.