|
|
|
|
|
by ottertown
4118 days ago
|
|
You don't have to go that far down the Backbone road to get performance that rivals other frameworks is the point. All this comes down to is how do you update the DOM when data changes. React nicely packages up that functionality for you, but in a huge dependency and in a fairly opinionated framework. For a lot of developers, the flexibility of Backbone is worth the incurred cost of having to manually create listeners / render actions for data updates. |
|
"For a lot of developers, the flexibility of Backbone is worth the incurred cost..."
Ugh. I could not disagree more. The "flexibility" that Backbone provides in allowing you to write manual DOM updates after an initial render is easily it's biggest down-side. This Backbone pattern to rendering data treats every data and state change as a 1-off situation after the initial render. Painful. "Flexibility"