I wouldnt think that creating scopes would really affect performance. Watches are the thing that will eventually slow you down (when you have many thousands). You should look at bindOnce (native in 1.3.10+ via :: prefix) if you find that an issues. In general, performance is quite snappy in most cases. Large lists are the downfall (create lots of watches) and so you should look to bindOnce of use a virtual scrolling library - which ony renders visible items. Otherwise i'd say, design your directives with functionality in mind.
On 10 September 2014 20:25, Sander Elias <[email protected]> wrote: > Hi Stacey, > > Isolated scopes are about separating concerns, not about performance. > That being said. the 'hit' you get on performance is barely measurable. I > can't say there isn't > one, but it's not worth worrying about. This is the don't optimize > prematurely all over again. > > Regards > Sander > > -- > You received this message because you are subscribed to the Google Groups > "AngularJS" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/angular. > For more options, visit https://groups.google.com/d/optout. > -- Tony Polinelli -- You received this message because you are subscribed to the Google Groups "AngularJS" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/angular. For more options, visit https://groups.google.com/d/optout.
