My colleague Julien can answer for himself, of course, but I’ll jump in right now and say that I agree with you.

In fact, the sane guidance you’re offering is what Julien provides to teams across the company. Knowing when *not* to do something is just as important as when to do something.

Thanks for the clarifying question.
Nate

Are you seriously evangelizing AJAX for regular navigation of webSITES? If so, I think you and/or your team are on the absolute wrong track, because navigation of websites is already solved, has been for 10+ years.

It’s for state changes in single page webAPPLICATIONS that we need to have custom history, because this kind of ‘navigation’ is not tracked by the browser.

It comes down to the difference between websites and webapplication, and I hope your team will not convince developers to create complicated navigation using javascript when the regular navigation is sufficient. The following quote is where I think the mistake is made (the simple website is not a rich application):

“Only recently did I find myself impacted in my own work by the absence of a good solution for managing navigation history and session state in a rich application. At the time, I was working on a very simple web site for my father’s new venture.”

So, the history manager is great and needed, but don’t advocate its use for regular navigation, emphasize the use in webapplications.

Good luck!