Menu
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.
938
Today, Knockout. js mostly exists in legacy applications and developers try to move to something newer, like Vue.
Learning curve As you can see, all of these frameworks are easy to learn but hard to master. Building the first application with Knockout is challenging because you'll need to write lots of custom adapters for third-party libraries. Development becomes easier once you finish writing the infrastructure code.
Knockout is a JavaScript library that helps you to create rich, responsive display and editor user interfaces with a clean underlying data model.
Knockout is a standalone JavaScript implementation of the Model–View–ViewModel pattern with templates. The underlying principles are therefore: a clear separation between domain data, view components and data to be displayed.
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.
http://www.geekdave.com/?p=79
Feedback is most welcome!
188
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.
20
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
