3 ms·
I can't quite tell why someone would want to use this framework over Knockout. The Knockout documentation is quite a bit more thorough and the two way binding
by dos1 14y ago
I can't quite tell why someone would want to use this framework over Knockout. The Knockout documentation is quite a bit more thorough and the two way binding looks to be more robust.
Also, both Knockout and Angular require that you add non-standard attributes to your markup. Whatever happened to separation of concerns? Having used both Knockout and Backbone, I find Backbone's separation of JS and HTML to be a major benefit. Not to mention two way binding is a neat trick, but often what I'm really after is a decent structure to hang my custom script on so I can keep it maintainable. A lot of the code I wrote using Knockout is almost impossible to follow a few weeks later.
- hnwh 14y agoDo you think dynamically adding the data-bind attributes might help with the separation of concerns or maintainability of knockout? If not, what do you think the biggest obstacle to maintainability is?
- dos1 14y agoI'm not entirely sure that data binding is a good approach in general. I spent quite a bit of time on a Silverlight MVVM project too, and the data binding there got to be more trouble than it was worth as well. Seems like data binding separates the what (user input causes model to update) from the how (markup bindings magically translate to updated model) and that just makes an unmaintainable mess.
- mrbonner 14y agoDitto, I just looked through the code and demo and it looks very similar to Knockout. Does anybody know what the performance would be? I heard Knockout performance is not that great with big DOM document comparing to Backbone.