Most of those complains seem to be pretty basic. To me the only interesting one is #4, about syncing models.
As for collections - how would you handle adding/removing objects in Spine? Backbone's collections just let you listen for add/remove events so you don't need to do any manual work there.
No. 4 is something which I've solved in Backbone.js with about 50 lines of (commented) code. It's a pretty simple setup inspired by Rails and it has solved this problem in all use cases I've had. I've put it in a Gist here: https://gist.github.com/2762417
Comments
Most of those complains seem to be pretty basic. To me the only interesting one is #4, about syncing models.
As for collections - how would you handle adding/removing objects in Spine? Backbone's collections just let you listen for add/remove events so you don't need to do any manual work there.
No. 4 is something which I've solved in Backbone.js with about 50 lines of (commented) code. It's a pretty simple setup inspired by Rails and it has solved this problem in all use cases I've had. I've put it in a Gist here: https://gist.github.com/2762417
Sure, pretty straightforward, thanks for the code. So, in the end, no strong points and no collections.