3 ms·
Backbone doesn't do data binding; it's a completely different thing. (That's why things like rivet and epoxy exist; because backbone doesn't do it right)
by shadowmint 13y ago
Backbone doesn't do data binding; it's a completely different thing.
(That's why things like rivet and epoxy exist; because backbone doesn't do it right)
- mattwad 13y agoCorrection: Backbone doesn't try to be the kitchen sink like Angular. Its source code is about 500 lines, and its docs say as much: "Two way data-binding" is avoided. While it certainly makes for a nifty demo, and works for the most basic CRUD, it doesn't tend to be terribly useful in your real-world app. Sometimes you want to update on every keypress, sometimes on blur, sometimes when the panel is closed, and sometimes when the "save" button is clicked. In almost all cases, simply serializing the form to JSON is faster and easier. All that aside, if your heart is set, go for it.
- billions 13y agoThis. I would add angular is good for teams requiring extensive structure. The cost is control. If you're building a corporate webapp, angular is great to keep everybody neat. If you're doing something unprecedented such as 3D rendering or a new UI element, angular will hinder more than backbone.