Add EventBus navigation to UI5 XACE - XML App Component With EventBus

Hi DJ, This is more of a question than anything else so feel free to ignore this pull request. ;-)

I was wondering why you state that the two app templates use the EventBus. It seems that instead you are coupling each "child" controller to the "root" controller for navigation.
If you use the EventBus as per the SDK's "best practices" it would look like my pull request here... I've added it as another template "...With EventBus".
If I debug into the bowels of the navigation - deep, deep, down, the .to()  and .back() methods do internally use the EventBus anyway but its not visible when looking at the code...

So - what is the best practice? The code between each is not particularly cleaner one way or the other; though by coupling the controllers its probably two or three lines less all up. What do you think is the best way to go?