-
-
Notifications
You must be signed in to change notification settings - Fork 10.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Backbone: data binding libraries / tools? #550
Comments
When I was looking at the options out there, it really fell down to:
I didn't like Knockback, simply because I felt like I was introducing more technical debt into the project (learn knockout-isms). I was really splitting hairs over the other two, and eventually choose ModelBinder. One problem I hit with Backbone.ModelBinder was I found binding collections a little difficult (edit: this seems very clearly explained in the documentation now). It definitely follows backbone's lead and tries to leave a lot of implementation decisions to you, which was ok with me. Though I felt things were a bit verbose at times. Now that both projects have evolved/marinated, I think I would chose Stickit over ModelBinder. Looking at epoxy though, the filters and computed properties look pretty cool. Im curious to hear from people with experience working with it. |
As a staunch Backbone purist, I'm fundamentally offended by all data binding functionality. But, I have to admit that StickIt is pretty nice and I would use it if I was forced to. |
@jgable Please do expand on this! Why so? Do you have any other recommendations? |
I was just joking, I'm a fan of StickIt. Backbone people just get tired of |
😊 That reference went right over my head that did. Hahaha |
+1 Stickit |
Closed in favour of #2144 |
From IRC we have some suggestions:
There are two particular areas I'd like to look into:
Any suggestions, recommendations, gists, demos etc welcome
The text was updated successfully, but these errors were encountered: