I've used Backbone.js, I've learned about Knockout.js; however, now I found out about Knockback.js. It is supposed to get the best out of the other two tried& proven frameworks. Do you have any experience with Knockback in production? I'm wary to use it since it doesn't seem to be mature enough.
Asked
Active
Viewed 8,182 times
32
casperOne
- 73,706
- 19
- 184
- 253
Mihai Oprea
- 2,051
- 3
- 21
- 39
-
1Both exist: http://kmalakoff.github.com/knockback/ – Mihai Oprea Mar 14 '12 at 14:55
-
The fact that knockout will be included in MVC4 would suggest it is reaching maturity and has a strong level of momentum behind it. – Mark Robinson Mar 14 '12 at 16:38
-
5@MarkRobinson - I think Mihai was referring to Knock**back**. KO is clearly prod ready and so is Backbone but I am not sure about KB. – madcapnmckay Mar 14 '12 at 20:48
-
@madcapnmckay - D'oh! Must stop skim reading questions! Thanks. – Mark Robinson Mar 15 '12 at 08:51
-
I wonder if this changed at all. – Mihai Oprea Jul 04 '13 at 12:14
-
1I wonder why they don't call it *boneout*.js? – Faust Mar 01 '14 at 18:09
-
@Faust ... or *backout.js*? Guess *knockout.js* just sounds that much more awesome... – user193130 Mar 15 '14 at 02:33
2 Answers
32
I've been using Knockback on a large multi-module project with good results. The docs and examples are unnecessarily complex, so I wrote a blog describing Knockback with some very simple examples and a JSFiddle to get you started.
Feedback is most welcome!
Dave Cadwallader
- 1,751
- 12
- 10
-
2just curious, how many people are working on the 'large multi-module project' that you mentioned? i agree with you about the docs. I've found all 3 (bb, ko, kb) to have spotty documentation – Cory Danielson Jul 11 '12 at 00:05
-
-
3@CoryDanielson: I manage a team of five engineers, but we're building the common infrastructure that will be used my dozens more engineers who will build actual modules. Also, despite all the research that went into supporting KO/KB, we've just switched to using Backbone.ModelBinder (https://github.com/theironcook/Backbone.ModelBinder) which has proven to be faster, and easier-to-understand. I'd strongly recommend it. Glad you're enjoying the subroute plugin! I just released v0.2 with some important bug fixes and new features. Check it out! https://github.com/ModelN/backbone.subroute – Dave Cadwallader Jul 16 '12 at 14:14
-
thanks for the update. At a glance, ModelBinder looks very useful. The team that I work on also decided to back away from Knockback and stick with Backbone... mostly due to the overhead in learning about 3 different libraries, higher potential for memory leaks, and because the community & support for backbone is unparalleled. Personally, I think Knockback is an awesome library and would be very fun to use on personal projects... I was pretty excited with how quickly i was able to get things working with it... – Cory Danielson Jul 16 '12 at 15:31
-
3The bloat of dependencies that comes with Knockback is pretty rough though, especially on mobile. jQuery, underscore, Backbone, Knockout, Knockback... it's quite a fat stack... for all the functionality that it provides, Ember.js may be more beneficial to look into. – Cory Danielson Jul 16 '12 at 15:31
-
1@CoryDanielson : I'm excited to see where Ember.js goes in the future, but for now it doesn't quite seem production ready, based on the size of the community, # of plugins available, documentation, etc. It does feel a bit like building a Frankenstein monster, sometimes, stitching together all these libraries. But such is the life of a JS architect these days! – Dave Cadwallader Jul 31 '12 at 18:29
6
I wouldn't use it yet. It's hard enough to get corporate buy in on knockoutJS.
I guess it all has to do with the size of your company, the willingness to support alpha / beta / volatile open source projects.
It is the nature of the beast, this bleeding edge of innovation. Skating that thin ice of unsuportability.
Brandon Wittwer
- 381
- 1
- 8
-
9FWIW, asp.net MVC 4 comes pre-loaded with Knockout.JS. And from what I know of it's creator Steve Sanderson, I don't see a problem with using it. Anyway, the success of production systems has more to do with the quality of the developer. I've seen people mess up production apps with Jquery. – PhillipKregg Mar 23 '12 at 02:13
-
Don't get me wrong. It's not impossible to get a large organization to adopt. I work in a $3b/yr organization and am more than half way through a 100% knockoutJS single page app. – Brandon Wittwer Mar 23 '12 at 02:53
-
1I totally hear where you're coming from as well. The additional requirement with any large organization is supportability. JQuery is well documented and widely accepted. Therefore it is easily supportable ( think 5 years later ). We've made the jump into knockoutJS hoping it will be a sustainable solution. So the question is "is knockBack going to be a long term supportable solution?" – Brandon Wittwer Mar 23 '12 at 03:01