6 ms·
Knockout is so, so good. I just wish it had proper API documentation. There are no real docs, only examples/tutorials, this can be quite frustrating. If you'v
by shaunol 13y ago
Knockout is so, so good.
I just wish it had proper API documentation. There are no real docs, only examples/tutorials, this can be quite frustrating.
If you've never used data bindings in HTML/JS, you HAVE to give this a try.
If you're still using jQuery & other manual event handlers to change the state of your UI, you GOTTA try it!
- speg 13y agoI just started building in knockout again after casual off and on use for the past couple years. At least those tutorials are very good!
- fournm 13y agoThis. Knockout's tutorials made me far more seriously look at it than Ember for a side project I was playing around with recently, coming from the position of not knowing either of them.
- camus2 13y agocant be worse than AngularJS doc... The doc doesnt make sense at all, the framework itself is not that complicated to use,but come on, the documentation is a shame,the new doc is even worse, less code exemples than before, nothing makes sense when reading it. Half the api is not explained. Instead of going with a simple rst / readthedoc format, they made (generated) something bloated and useless. I'm a huge Angular fan,but come on,it's not a little open source project,Google has the money to hire 1 person that can write docs...
- warp 13y agoThe documentation seemed fine to me. What is missing from http://knockoutjs.com/documentation/introduction.html http://knockoutjs.com/documentation/introduction.html in your opinion?
- jf22 13y agoIf you've never done a SPA before just skip knockout and head to angular or ember. Your app can out grow knockout and then your stuck rolling your own location provider,dependency injection and more. 2-3 years ago knockout was a breath of fresh air but know its just old and dated technology.
- shiz 13y agoCan you elaborate on why knockout is old and dated? It's HTML and JS, just like the others. And compared to the bloat that is angular and especially ember, I find knockout strikes with simplicity and 'keeping-it-simple'.
- taude 13y agoIt's not. And not everything should be architected as a SPA, but more likely multiple page SPAs. Your users probably don't go to every module of a large app with the same frequency...
- sehr 13y agoOr you can just wire up different libraries as needed and forgo the usage of a entire framework...
- skilesare 13y agoKnockout + Backbone Router is all you really need. It will save massive headaches from trying to shoe horn something in to angular or ember.
- taude 13y agoWe didn't actually find the documentation and examples that bad. I had a team of heavy front-end (html/css/Jquery) developers get up to speed in knockout fairly easily. It would have been a nightmare explaining to them how to make Angular directives and some of the more complex services stuff. BTW, I think Knockout is just prescriptive enough to get a pretty tight maintainable codebase, but without causing another layer of wrapping/complexity when you want to use existing JQuery components.