3 ms·
> Many web applications are now foregoing client-side templating and are back to doing it on the server. GitHub is a great example of this, and Twitter is going
by nailer 15y ago
> Many web applications are now foregoing client-side templating and are back to doing it on the server. GitHub is a great example of this, and Twitter is going this route too.
They had client side templating, and they switched back to server-side? Got any links for that, I'd love to read them (seriously, not snarkily).
- dmix 15y ago37signals recently posted about using PJAX and server-side templating to rebuild Basecamp. Theres a counterpoint of linkedin moving towards client side with dust.js: http://engineering.linkedin.com/frontend/leaving-jsps-dust-moving-linkedin-dustjs-client-side-templates http://engineering.linkedin.com/frontend/leaving-jsps-dust-m... But I'm also interested in hearing about twitter/githubs change of heart.
- scotth 15y agoNo, they didn't. Pop the inspector's network panel open and watch what happens on Twitter. All the content comes down as JSON.
- andybak 15y agoThe claim is that they in the process of switching back, not that it's already rolled out.
- lapusta 15y agoThey were switching from hashbang routing to pushstate, not from client to serverside rendering. Although they might to pre-rendering for IE, which will get support of pushstate only in version 10. http://storify.com/timhaines/hashbang-conversation http://storify.com/timhaines/hashbang-conversation
- andybak 15y agoHopefully they are going with pushState with a fall-back to server rendering for all user agents that don't support pushState. That's a compromise I can get behind. And it's pretty much progressive enhancement...
- bricestacey 15y agoI thought they were simply changing over to compiling their mustache templates on the server to speed up the process.