4 ms·

We need to get back to server-side cached rendering. Thinking mobile-first and lightweight websites. I feel in the last few years we've added so many things and

We need to get back to server-side cached rendering. Thinking mobile-first and lightweight websites. I feel in the last few years we've added so many things and we are no thinking on the people with slow internet. Ember FastBoot now this, Angular 2 coming with it. We are going towards hybrid awesome front-ends which load fast and deliver the best UX we've had. Thank you for the great effort.

firasd 11y ago
For sure. I was always uncomfortable with JS frameworks that used markup with no content from the server. In my professional experience I've also found that developers underestimate how slow Ajax requests are in real world scenarios. I wrote some comments on this when I started learning React, just gonna screenshot them instead of pasting: http://i.imgur.com/XSnCqjK.png http://i.imgur.com/XSnCqjK.png Two great articles I reference in this tutorial: 1) http://tomdale.net/2015/02/youre-missing-the-point-of-server-side-rendered-javascript-apps/ http://tomdale.net/2015/02/youre-missing-the-point-of-server... 2) http://rauchg.com/2014/7-principles-of-rich-web-applications/ http://rauchg.com/2014/7-principles-of-rich-web-applications...
awalGarg 11y ago
I am curious how this would change with the multiplexed pipe of HTTP2 where doing a lot of requests is not as expensive. I did a couple little tests a while ago with nginx 1.9.1 mainline, and while the results did show a little performance improvements in figures, they weren't observable - but this could be because I didn't put in much care while doing those tests and I probably did some mistakes. Anyone else has done good benchmarks on real world single-page-apps which do a lot of back-n-forth communication with the server with http2? I don't expect things to get suddenly extremely better (specially since resource fetching is only one of the bottlenecks), but maybe it could bring a mid-way between the server vs client side rendering war.
- frandroid 11y ago
  HTTP2 will help, but it'll also make server-side rendered pages load even faster, before you load all of your client-side JS.
SeeDave 11y ago
I agree, to a certain extent, but mostly for the initial load. I remember reading an interesting article about how twitter does exactly this with "time to first tweet" being the defining metric. Beyond that, I think stateless services/web sockets/DOM-manipulation would best serve users who have a need for real-time updates and dynamic content. For reference: https://blog.alexmaccaw.com/time-to-first-tweet https://blog.alexmaccaw.com/time-to-first-tweet

firasd 11y ago

For sure. I was always uncomfortable with JS frameworks that used markup with no content from the server. In my professional experience I've also found that developers underestimate how slow Ajax requests are in real world scenarios. I wrote some comments on this when I started learning React, just gonna screenshot them instead of pasting: http://i.imgur.com/XSnCqjK.png http://i.imgur.com/XSnCqjK.png Two great articles I reference in this tutorial: 1) http://tomdale.net/2015/02/youre-missing-the-point-of-server-side-rendered-javascript-apps/ http://tomdale.net/2015/02/youre-missing-the-point-of-server... 2) http://rauchg.com/2014/7-principles-of-rich-web-applications/ http://rauchg.com/2014/7-principles-of-rich-web-applications...

awalGarg 11y ago

I am curious how this would change with the multiplexed pipe of HTTP2 where doing a lot of requests is not as expensive. I did a couple little tests a while ago with nginx 1.9.1 mainline, and while the results did show a little performance improvements in figures, they weren't observable - but this could be because I didn't put in much care while doing those tests and I probably did some mistakes. Anyone else has done good benchmarks on real world single-page-apps which do a lot of back-n-forth communication with the server with http2? I don't expect things to get suddenly extremely better (specially since resource fetching is only one of the bottlenecks), but maybe it could bring a mid-way between the server vs client side rendering war.

frandroid 11y ago
HTTP2 will help, but it'll also make server-side rendered pages load even faster, before you load all of your client-side JS.

SeeDave 11y ago

I agree, to a certain extent, but mostly for the initial load. I remember reading an interesting article about how twitter does exactly this with "time to first tweet" being the defining metric. Beyond that, I think stateless services/web sockets/DOM-manipulation would best serve users who have a need for real-time updates and dynamic content. For reference: https://blog.alexmaccaw.com/time-to-first-tweet https://blog.alexmaccaw.com/time-to-first-tweet