If the difference in experience between web and desktop apps is going to keep decreasing, eventually, I think the stack of technologies will be completely changed.
1) HTML/CSS for templating 2) JS for state management. 3) HTTP for data persistence/distribution.
I don't think technology stack will change radically, rather, new frameworks will be created and old frameworks updated to fit this paradigm. We are beginning to see that in the current wave of client side frameworks - Ember, Angular, Batman, etc.
It seemed to me that Turbolinks while improving page response, does not address data-binding/modeling and offline/low bandwidth support which seemed to be the path taken by the clientside frameworks towards making JS as a state manager.
Why? Does the tiny electronic miracle on your lap or desk that is more powerful than the sum of all computers that existed in the world in 1970 have something important to do or something?
It is not about performance savings, it's about the user experience. Functionality like this can be baked into websites today (basecamp-next et al), but surely it will get easier (I am thinking semantic element which already tell the browser what is a <nav>).
