That's not really my experience, nor do I really understand why people seem to say knockout and backbone in the same breath so often.
There is very little overlap in the goals of these two frameworks. The approach is fundamentally different. You could, realistically, even use both in parallel with a few tweaks.
We use knockout in a large scale app (75 person company) and as just a single small component in our stack that really only handles UI bindings and gives our viewModels a bit of structure it's been very solid so far.
We don't use vanilla knockout, we rolled our own data binding and sandboxing. But if you're writing a 'large app' and your architecture doesn't let you swap out components in your stack at will, be it jQuery, knockout, backbone, sammy, without touching anything outside those boundaries then it's not a good sign!
There is very little overlap in the goals of these two frameworks. The approach is fundamentally different. You could, realistically, even use both in parallel with a few tweaks.
We use knockout in a large scale app (75 person company) and as just a single small component in our stack that really only handles UI bindings and gives our viewModels a bit of structure it's been very solid so far.
We don't use vanilla knockout, we rolled our own data binding and sandboxing. But if you're writing a 'large app' and your architecture doesn't let you swap out components in your stack at will, be it jQuery, knockout, backbone, sammy, without touching anything outside those boundaries then it's not a good sign!