Correct. This is no fault of Ember's; it's just a characteristic of the language that I dislike.
23 karma · joined April 13, 2012
> 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.