3 ms·
The documentation on these frameworks isn't great. In fact, it's downright horrible. There are no conventions or standard practices and every tutorial I can f
by atomical 15y ago
The documentation on these frameworks isn't great. In fact, it's downright horrible. There are no conventions or standard practices and every tutorial I can find builds an application with these frameworks in a different way.
- kennystone 15y agoThe docs are ok, but example code and tutorials are lacking. Peepcode showed me the way, but it's not free.
- derickbailey 15y agothat's one of the benefits and drawbacks of them, really. it's great to have flexibility, but it makes learning them more difficult because there's no hand-holding. it may require someone that has already formed opinions, to guide you through the learning process.
- atomical 15y agoWell, the hand holding is basically showing you how to build a simple application that has a few buttons and a few input fields. It's sort of like reading the simple 5 line example of how fork() works in a 101 class. The author writes 50 line programs for computer science books. However, when you're writing an application with a bigger scope the simple 50 line example isn't much use.
- jonmc12 15y agoI found http://learn.knockoutjs.com/ http://learn.knockoutjs.com/ to be a very nice intro to knockout.js. For Backbone, docs + annotated source are more than sufficient. Best practices - I stick to simple rule of using Views (in backbone) and view models (in knockout) to interact with dom, then using models in both frameworks to sync w/ DB. This keeps code fairly clean, and use of other components of framework relatively straightforward.