4 ms·

yes, that's an accurate statement. backbone and knockout focus on two different problem spaces: app architecture (backbone) and UI wizardry (knockout). there

• amalag 15y ago
  There is so much proliferation of javascript mvc plugins. From a user point of view, makes deciding very difficult. I basically looked at the two big contenders and went with knockout because it solved what i thought was the more pressing issue. As for model persistence, for my use case, i don't mind if it is only updated to the server with a submit, then i will push some json to the server and i can parse the complex object to save it. It is the javascript stuff that wastes the majority of my time on complex 1 page apps and is why I wanted something to help clear that up. I am sick of writing jquery onchange and other event codes for select boxes, etc. It always seems like an after thought, but if we are designing our ajax functionality from the start then we need a library which can handle it. For instance there is no standard or canonical way to do multiple depdendent cascading dropdowns in rails. For that I will roll it out by requesting a complex object once, then binding the select boxes, and it's done. No onchange events and multiple ajax requests. Anyway there are so many javascript mvc frameworks and i am really not qualified to judge their programming merits. I just have to go with what is likely to be maintained in the future, what works, and what has good documentation and user groups.