Could not agree more. Learning data-driven UI's, coming from a declarative world like jQuery is really tough. It takes some getting used to. Especially avoiding the temptation to pollute your view models with jQuery selectors, thus violating the MVVM principles. I ended up becoming an expert on Knockout and helped train some of our team how to use it properly. Two years ago I built an entire POS application using it, and we didn't experience any performance issues whatsoever. So long as you use components, deferred updates and ko.pureComputed (instead of ko.computed, it will perform amazingly. It's not a popular library (intentionally not calling it a framework). But it's f***ing awesome!
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Could not agree more. Learning data-driven UI's, coming from a declarative world like jQuery is really tough. It takes some getting used to. Especially avoiding the temptation to pollute your view models with jQuery selectors, thus violating the MVVM principles. I ended up becoming an expert on Knockout and helped train some of our team how to use it properly. Two years ago I built an entire POS application using it, and we didn't experience any performance issues whatsoever. So long as you use components, deferred updates and
ko.pureComputed(instead ofko.computed, it will perform amazingly. It's not a popular library (intentionally not calling it a framework). But it's f***ing awesome!