Tom Dale wrote a great piece about he and Yehuda Katz are rethinking routing and how it can be done more intelligently for ember.js.

Having written more apps than I'd like to remember, routing has always been a pain-point. This is because managing state (or rather, true state) is a non-trivial problem requiring that we we figure out and store exactly what changes in configuration have occurred during their time on a page.

Sure..simply routing them to a view populating data gives us some sense of bookmarkability, but I'm really excited to see just how far Tom and Yehuda can take these ideas.
Shared publicly