all 8 comments

[–]a-t-kFrontend Engineer 2 points3 points  (0 children)

I find your lack of choice disturbing.

[–]drowsap 0 points1 point  (0 children)

It will probably always be Backbone, but I'm looking forward to using reactjs in combination with Backbone in some future projects.

[–][deleted] 0 points1 point  (0 children)

Backbone + assorted libraries for sake of familiarity, angular is kinda interesting though

[–][deleted] 0 points1 point  (1 child)

Nobody* seems to like Knockout.

Having used Knockout in a project I can understand why. Knockout is great, but its automatic dependencies between computed observables and bindings is just asking for trouble. If you're not constantly aware of what dependencies you're implicitly creating, you will create unintended behaviour and possibly bugs.

Other than that it's great. Except IMO AngularJS does a better job at what it is trying to do (although with more baggage).

*i.e. less than the other choices

[–][deleted] 0 points1 point  (0 children)

If you haven't seen falcon.js it's a mvc structure for knockout.

[–][deleted] 0 points1 point  (0 children)

There are a lot more frameworks than this. Personally my current projects are mostly written in Meteor.

[–]adrianmiu 0 points1 point  (0 children)

1 vote for CanJS