Hacker News new | ask | show | jobs
by yankoff 4960 days ago
Exactly. But I'd go further with this thought. I think big part of the problem are technologies that are used to build Web apps. HTTP, HTML/CSS and even JS are good exactly for what they were supposed to be good for: creating simple documents and serving them one by one by request. And we are using them to try to build real software.

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.
2 comments
jasonong 4960 days ago
My simple software worldview is as follow.

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.

link
mattsjohnston5 4960 days ago
Do you see this new stack of technologies as a gradual evolution of our current stack, or do you feel the technologies are inherently broken and need to be replaced completely?
link