Yes, directives are fairly low-level. In that sense, saying that they “solve too many problem spaces” is like saying “functions solve too many problem spaces”. As I pointed out in the last post, they are simply a way to bind javascript to DOM, and they exist to make it easy to create flexible higher-level constructs, as evident by how a angular’s pseudo-templating is implemented by directives such as ng-bind, ng-repeat, ng-if etc…
As you have pointed out, you are free to implement directives in a way that matches how you currently do things. All I’m pointing out is that I’ve had plenty of experience in porting projects form other frameworks and styles to angular and have seen time and time again how drastic the reduction in both code size and complexity can be when things are done “the angular way”. By “angular-way” I am mostly referring to proper declaritive templates bound to “MVVM” style models. Mind you, I don’t really have much details about your current home-grown framework that you are using, so I can’t really comment or compare it to anything. But I look forward to any further questions you may have and discussing any pros and cons of either method. -- 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/groups/opt_out.
