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.
Yeah I'm glad I didn't have to go through all that to realize that happiness and satisfaction has to start NOW. Don't push it off to some rose-tinted future of the ROI of investing heavily in a startup. Startups should be built with sustainable happiness in mind.
Disclaimer: I did my own startup in 2009 via debt financing, only to wake up daily with a sad, solemn face because I did it at the expense of my family, friends and my life purpose.
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.