That's treating the application as if it were completely stateless, and mucks with browser history. A good example of when to use state vs. a route is on a del

That's treating the application as if it were completely stateless, and mucks with browser history. A good example of when to use state vs. a route is on a delete. If I route to a delete, for example, then it might fire again when I hit my 'back' button, which is obviously a bad idea. Derick Bailey has a good article on it here: http://lostechies.com/derickbailey/2011/08/03/stop-using-backbone-as-if-it-were-a-stateless-web-server/ http://lostechies.com/derickbailey/2011/08/03/stop-using-bac...