Vlad Balin

Because of that, I would rather prefer having client-side state management technologies to be client/server transport and protocol neutral (which Type-R and NestedTypes really are - there are just _two_...

That's the good point, and as I said it can be done pretty straightforward taking Type-R and implementing GraphQL I/O layer on top of it. To define GraphQL schema using...

I can help with that if you will decide to do it. It will be fun.

Regarding the problem of updates. In our case, we are using REST for bulk data requests and websocket for pinpoint real-time updates. For instance, if we have the large model...

@far-blue, so what did you decided? As I said, I can help you with the project based on `Type-R` which will use GraphQL as an I/O medium. Fork the NestedTypes...

Sure. Just keep in mind that I will help if you decide to make it.

added and removed - that's easy. Problem is to track changed models... Easiest way of doing this is to maintain `changed` hash, which is filled in on model's change event....

collection.fetch, and all model I/O methods (save, fetch, destroy), are currently returning promises (this feature is standard for backbone). So, you could do right now: ``` collection.fetch().done( () => this.render()...

But the most common pattern we're using is the following line in View.initialize: `this.listenTo( this.model, 'change', this.render )` And view will be rendered for every change no matter what the...

You can do all that stuff with React views, and it looks and works nicer, but that's a bit different story. I will release updated version of React bindings soon....