> And if they all want to use it - let them use it. The productivity gained by agreeing on a framework usually outweighs the performance loss over the "best" so

> And if they all want to use it - let them use it. The productivity gained by agreeing on a framework usually outweighs the performance loss over the "best" solution. I totally disagree, and not because of performance; choosing a framework based on its performance would be premature optimization. Your argument breaks down here: > I'll be damned if I make them learn my way of doing things. I'd expect these devs to implement a feature quickly But that's exactly what a lot of projects using a framework end up doing. Between Ember, Angular, React, Backbone, Dojo, Prototype, and GWT, there is a ton of competition in this space, and you would have a hard time finding a team of professionals who all know the same framework. So at least some of your team will be learning the framework, and that learning will not pay off compared to just using vanilla JS. You can't argue that familiarity outweighs the complication added by a framework because people aren't familiar with the same frameworks. Vanilla JavaScript is the lowest common denominator: almost everyone is familiar with it.