News for hackers. Stuff that matters.
Re:Blazing fast node.js: performance tips from LinkedIn by karterk on Sunday June 24, 2012 @01:25PM (#4153713)
It's interesting to note that while Twitter has moved away from client side rendering of HTML templates (and is a strong advocate of sending HTML directly down the wire[1]), LinkedIn mobile app seems to be rendering the template on the client.

[1]: http://engineering.twitter.com/2012/05/improving-performance...

Re:Blazing fast node.js: performance tips from LinkedIn by chime on Sunday June 24, 2012 @01:54PM (#4153769)
Just because client-side rendering did not work well for Twitter for a variety of reasons, does not mean it is subpar to server-side rendering in all cases. Performance-wise, if server_json_generate + json_download + client_render_json_to_html < server_html_generate + html_download + client_render_html, you can certainly go with client-side rendering.

In Twitter's case, client-side rendering was slow while server-side wasn't. In LinkedIn's case, html_download was slow while client_render_json_to_html wasn't. Performance aside, there are numerable reasons to go either away, all of which vary from project to project.

Having Worked with CoffeeScript + Twitter Bootstrap + BackboneJS/Underscore + LessCSS for some time now, I know I will not willingly go back to the old server-side ways unless there is a major reason to. Working fully client-side to make UI and relying on REST API / JSON is wonderful experience, especially when the app feels so responsive.

Re:Blazing fast node.js: performance tips from LinkedIn by jameswyse on Sunday June 24, 2012 @11:00PM (#4154896)
What about SEO? I've noticed a lot of these sites that are rendered client-side start with very little content in the HTML, doesn't this mean the search engines can't read the content?
Re:Blazing fast node.js: performance tips from LinkedIn by cynwoody on Sunday June 24, 2012 @11:36PM (#4154967)
According to this other LinkIn blog post, http://engineering.linkedin.com/frontend/leaving-jsps-dust-m... (look for SEO in the comments), they detect cases where the client can't or won't do JS and perform the rendering server-side.
Re:Blazing fast node.js: performance tips from LinkedIn by Marwy on Monday June 25, 2012 @04:07AM (#4155569)
How do they do that? I can't really figure out anything apart checking user agent (for web crawlers?)
Re:Blazing fast node.js: performance tips from LinkedIn by heroic on Monday June 25, 2012 @07:39AM (#4156028)
you can simply check for the accepts header.
Re:Blazing fast node.js: performance tips from LinkedIn by rhizome on Sunday June 24, 2012 @02:03PM (#4153801)
Can we assume that degradability isn't a concern for you? Accessibility?
Re:Blazing fast node.js: performance tips from LinkedIn by chime on Sunday June 24, 2012 @02:29PM (#4153861)
Degradability is not a concern. Accessibility is, and client-side rendering does not mean no accessibility.
Re:Blazing fast node.js: performance tips from LinkedIn by rhizome on Sunday June 24, 2012 @02:06PM (#4153808)
I'm a bit bemused that for me, I can't think of an area where LinkedIn is anything more than a straight HTML site. That is, why would they need something like this?
Re:Blazing fast node.js: performance tips from LinkedIn by Domenic_S on Sunday June 24, 2012 @08:25PM (#4154619)
Why would they need a template engine? Erm.. because they have more than one user....
Re:Blazing fast node.js: performance tips from LinkedIn by rhizome on Monday June 25, 2012 @02:23PM (#4157844)
I mean to say that there doesn't seem to be any apparent use of node on LI. Is there a chat facility or something?