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.
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.