News for hackers. Stuff that matters.
Re:Leaving JSPs in the dust: moving LinkedIn to dust.js clie... by reinhardt on Tuesday December 13, 2011 @07:27PM (#3350037)
"All told, we evaluated 26 different templating technologies, scoring them on a variety of factors: DRY, JS library agnostic, mature, open source, easy to learn, documentation, flexibility, performance, and so on."

If anyone from Linkedin is reading - any chance of getting this evaluation posted somewhere? Would be useful even if it's just a "tech x factor" matrix without commentary.

Re:Leaving JSPs in the dust: moving LinkedIn to dust.js clie... by vybs on Tuesday December 13, 2011 @11:10PM (#3350536)
Sure, we should be able to make it available on the blog site.
Re:Leaving JSPs in the dust: moving LinkedIn to dust.js clie... by toonketels on Wednesday December 14, 2011 @12:24AM (#3350753)
That would be great. I also would love to see the see the matrix.

Any change you are going to discuss in more detail how to use the js templates on client and server side?

Re:Leaving JSPs in the dust: moving LinkedIn to dust.js clie... by vybs on Wednesday December 14, 2011 @04:12AM (#3351169)
Sure, we'd like to soon write more about this. Node.js and jvm based rhino are the two solutions we are trying out internally. We are building some of our seo use cases with dust templates and server-side rendering. It is quite easy and efficient to reuse the same template for both non seo and seo cases