[marknutter]

Learning directives, services, and the scary sounding "transclusion" has not been an issue at all for my team and I who are using angular on a very large project and loving it. Directives are quite simple once you understand the basic principles. Transclusion when actually explained (http://www.egghead.io/video/cjrBTjMvruI) is a trivial and obvious concept. I understand the confusion one may have around services/factories/providers because they are all very similar and in some ways little more than syntactic sugar for a single API, but once their differences are sorted out as in this blog post (http://iffycan.blogspot.com/2013/05/angular-service-or-facto...) they too become very natural.

[pzuraq]

For me it wasn't learning the terms, I didn't have an issue there. The problem was how limited Angular was in comparison to Ember, particularly the idea of directives. I actually spent a large amount of time on freenode discussing in the Angular chatroom how I might construct a directive to replicate a common jQuery plugin like Zurb's Joyride. In short it couldn't be done in anyway that seemed remotely non-hackish.

Ember has jQuery included, so using existing plugins is generally easy or at least possible. Beyond that, it has a far more powerful router (try doing deep routing with Angular. Angular UI's router may be changing this, but you would still have to include outside code to get the power of the standard Ember router) and in the future much more powerful REST support with Ember-Data (currently volatile, but still very powerful).

I started building a large application with Angular using FuelPHP for the REST server. Angular simply didn't have the power to do the things I needed it to at that time. Hopefully that's changing, since it seems to be the dominant framework these days.