Re:A Comparison of Angular, Backbone, CanJS and Ember
by porker on Wednesday April 17, 2013 @08:54AM
(#5564154)
Best practices and a large-scale app would be awesome!
The people in the IRC channel are very helpful (and will happily tell a cleaner way to do it than the KO examples on their website), but to have all this written up would be excellent.
Re:A Comparison of Angular, Backbone, CanJS and Ember
by WickyNilliams on Wednesday April 17, 2013 @10:45AM
(#5564752)
Thanks for the tip about the IRC channel, didn't realise there was one out there. I assume it's on freenode?
But for most, hitting up an IRC channel is a barrier to entry they just won't have the enthusiasm to overcome. Such advice should be front and center, easy to access, up to date and canonical.
Re:A Comparison of Angular, Backbone, CanJS and Ember
by porker on Wednesday April 17, 2013 @12:39PM
(#5565430)
Freenode indeed :)
Re:A Comparison of Angular, Backbone, CanJS and Ember
by Lazare on Wednesday April 17, 2013 @03:21PM
(#5566482)
Knockouts documentation is fantastic, but geared at a very novice level. The lack of any guidance on unit testing is a particular frustration.
Re:A Comparison of Angular, Backbone, CanJS and Ember
by WickyNilliams on Thursday April 18, 2013 @07:02AM
(#5569849)
I agree. The documenation is awesome. Concise, accurate and not confusing (i'm looking at you angular). And the interactive online tutorial is the icing on the cake. I posit that a complete beginner could get up and running with KO within a few hours.
But again, for non-beginners, I'd like to see more in-depth stuff.
Personally I think KO would greatly benefit from more architectural guidance (as i mentioned above). You're left on your own architecturally and structurally, with little guidance or higher level constructs to assist. This is much like backbone, but with backbone there is a lot of guidance out there, and even frameworks built atop of it (e.g. Marionette) which aim to instil best practices.
Things I'd like to see, which might quell other's trepidation:
* A large-scale demo app, with a detailed run-through of the how's and why's
* A guide to unit testing ko apps
* Drop IE6 (maybe even IE7?!) support to make it super lightweight. It's never going to be backbone lightweight, but imagine being able to say the tiniest front-end framework with no dependencies - that's a powerful message