It seems that keeping statefullness on the client side in the browsers memory is a trend we are heading towards. XMLHttpRequest allows us to load the UI of a web application and then create, read, update, and delete information from the server without reloading this initial shell. Many of these types of new applications actually version the application resources that are download, since you can't assume your user will reload the application with each click. When code is pushed out on the server side, a reload can be triggered to the user's UI resources and frontend scripts. Developers should start profiling browser memory usage, as these long running pages without a refresh could become bloated hogs without careful regard to memory allocation. Once data is no longer being used, it should be removed or nulled out from any in memory collections for example. It is interesting to think about how this new tool can change development concerns and abilities.