I like the author's focus on results and team productivity. Standardized tools are key for that. This is also my main concern, when it comes to JavaScript frame

I like the author's focus on results and team productivity. Standardized tools are key for that. This is also my main concern, when it comes to JavaScript frameworks and libraries. While Ember seems very good at that front, when talking about a single project or multiple very similar projects, I would like to add another point: As soon as you are working with different platforms (the author mentioned WordPress), you should not necessarily integrate everything all the way up. Because now you have your Ember based build process and maybe something gulp-based for WordPress. I always try to find frameworks, which has all the things only concerning itself integrated into (say server-side rendering etc.) but then stops there and makes use of preferably the two or three leading tools (e.g. grunt/gulp plugin) for all the other concerns. That way you can choose a standard stack and only consider new frameworks if they work reasonably well with it.