One approach is to explain that they are two different tools. Angular’s creator describes it as a metaframework - a framework for creating your application’s framework. Thus, if you get two different Angular apps, their internals will look completely different.
This is not the approach Ember takes, where you buy in to the framework’s conventions. So, one could argue that once you learn the conventions, you’ll spend much less time on boilerplate writing a new Ember app than a new Angular app. This doctrine also belongs to Rails, and it’s worked out pretty well for them.