I figured you probably meant React view :) I do a mental substitution of Backbone.View -> React Component whenever I use Backbone and React together.

I haven’t experienced much pain from not listening to the change event, if anything it forces me to compose my React components better, which is probably a good thing.

On May 25, 2014, at 2:15 PM, Mark IJbema <notifications@github.com> wrote:

> In README.md:
> 
> >    }
> >  });
> >  ```
> >  
> > -If you need to use multiple models, you can do so by including the mixin multiple times:
> > +React.Backbone also plays nicely with `Backbone.Collection`. Anytime the `add`,
> > +`remove`, `reset` or `sort` events are triggered the component will re-render.
> > +
> > +```javascript
> > +var UsersListView = React.createBackboneClasss({
> > +    render: function() {
> > +        var usersList = this.getCollection().map(function(user) {
> > +            return <li>{ user.get('name') }</li>;
> Oh sorry, I meant backbone views as react views ;) Bit confusing. Currently react backbone components don't listen deeper than one level. So changes to the collection, but not changes to the models in the collection. I don't actually use the Backbone.View. We could listen to change, but it would cause more rerenders. I don't really know if it would be too much though.
> 
> @clayallsopp did you exclude change intentional for performance reasons?
> 
> —
> Reply to this email directly or view it on GitHub.
>