I can appreciate that that (and the similar stories in reply) would happen. I recently successfully developed a complicated application using Knockout, but it i

I can appreciate that that (and the similar stories in reply) would happen. I recently successfully developed a complicated application using Knockout, but it involved fully committing to the rather strict computation model that is implied. I also had to modify and extend the core of the library. I'd say that Knockout can be suitable for large applications, but that you need to handle having an unusual computational model pervade your code. If you're interacting with existing code, it can be tricky to get inputs and outputs mapped correctly, but the knockback library mentioned in the article probably solves that for backbone users. One rule of thumb that might be useful is that any (non-event-handler) function you give to Knockout must handle being called an arbitrary number of times at arbitrary times, with some inputs being potentially outdated. If it cannot, you're not using the computational model the library essentially requires.