Great article!

I’d also like to know your take on Ember.

We have a few production applications built on Angular 1.x, and I’ve been following the development of Angular 2.x. But when we were faced with the decision on what frontend tech to use on a new project we decided to go with Ember.

The main reasons for the decision were:

• Angular works great, but isn’t opinionated enough. We find that this leads to developers in our team solving the same problems in inconsistent ways that all ‘work’, but creates a nightmare to maintain.
• Context switching between applications is nontrivial. Both of our main applications are built with Angular, but from different templates / generators. The difference is quite significant.
• We’re not that excited about upgrading our applications to Angular 2.x, as it seems that we will more or less need to rewrite the applications.

From our list above, it was clear that we had to look at alternatives.

When faced with learning something new, while building a production application, the idea of Ember + Ember-cli made more sense to us. We really needed less options and more opinion from our frontend framework.