I considered adding breaking that down further; it's definitely more complex than that. The thing is rails "models", "controllers", "routes" are still there in the Ember version. The point is added concepts, structure, files, etc. with Ember.
Hi there. I omitted the hashbang just because I find it ugly.
> Loading those other routes first either loads data or modifies the state of the application in a way that is required to display that route
That should be a non-issue as far as I understand, because visiting a nested route causes the parent route code to be executed first. Hence, the confusion.