Looking for advice: 

A dev team I work closely with has been using components pretty liberally 
to encapsulate functionality and templates. In general, these components 
are small, and do pretty simple things in their controllers. From a code 
organization and encapsulation perspective, this is really nice and things 
are easier to find/read. The only thing I'm concerned about is that in most 
cases, these are not components that have a lot of reusability. They are 
really intended to declutter the markup and parent view controller. I'm 
worried that the overhead of having to compile all of these components will 
degrade rendering performance. I haven't been able to measure this yet 
though. Anyone have any experience with something similar? Should I tell 
them to only make components for things that are reused?

-- 
You received this message because you are subscribed to the Google Groups 
"Angular and AngularJS discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to angular+unsubscr...@googlegroups.com.
To post to this group, send email to angular@googlegroups.com.
Visit this group at https://groups.google.com/group/angular.
For more options, visit https://groups.google.com/d/optout.

Reply via email to