News for hackers. Stuff that matters.
Re:Backbone vs Ember by learc83 on Thursday February 16, 2012 @02:44AM (#3597780)
>modifying a large collection, at the moment, can trigger the entire collection to re-render which can be extremely expensive.

How large is large enough to cause problems?

Re:Backbone vs Ember by bcrescimanno on Thursday February 16, 2012 @11:49AM (#3599483)
It really depends on your environment and the complexity of the rendering tied to your collection. For example, on a fast desktop-class system with a collection that renders one element with 1 property, you can probably have hundreds (or maybe even thousands) of items in the collection before you start to notice slowdowns when the collections update. Working on lower-end and mobile platforms, those numbers change. Similarly, if you rendering is complex, it will take more time as well. All that said, there's really no "magic number"

There are definite workarounds such as setting up paging--but the simple approach of using Ember.js bindings to bind a collection to a template will fall to pieces as that collection grows.

Re:Backbone vs Ember by sbarre on Thursday February 16, 2012 @08:59AM (#3598580)
I would also like to know this. :-)
Re:Backbone vs Ember by tbatterii on Thursday February 16, 2012 @09:08AM (#3598625)
me as well.