The whole "use lots of little modules" idea is great on the surface, but when you have to build large applications with small teams, I find it fails: - There a

The whole "use lots of little modules" idea is great on the surface, but when you have to build large applications with small teams, I find it fails: - There are always multiple choices for each piece of functionality you need to address, and personality clashes over which is the "best". - Security is a whole lot harder to nail down with more moving parts. Go with Angular, you have this: https://code.google.com/p/mustache-security/wiki/AngularJS https://code.google.com/p/mustache-security/wiki/AngularJS. Similarly, Ember: https://code.google.com/p/mustache-security/wiki/EmberJS https://code.google.com/p/mustache-security/wiki/EmberJS. Even though these frameworks aren't 100% secure (although Angular comes pretty close), you can be more aware of the pitfalls. The more independent modules you have to keep track of in your app, the more difficult it becomes to track security flaws. - Some seemingly unrelated components just don't end up playing nice with each other, and this can be hard to determine ahead of time.