CODEWITHSUNDEEP
javascripttemplatesclient-sideserver-side
Yevgeniy Brikman
Yevgeniy Brikman

Reputation: 9361

Templating language for both client-side and server-side rendering

I'm investigating JavaScript templates as a way to render our views. The goal is to be able to render client-side for users that have JavaScript enabled to to render the same templates/data server side for those users (and crawlers) that don't.

Requirements

  1. Client side rendering.
  2. Server side rendering (JVM support a nice-to-have).
  3. Reasonable support for loops, conditionals, text manipulation, partials, macros and extensions/plugins.
  4. Reasonably big/active community of users.

Unsatisfactory solutions found so far

  1. Mustache: supports server and client side rendering, big/active community, but the "logic-less" templates seem very restrictive and painful.
  2. Node.js plus underscore: JS templates like underscore provide all the template flexibility I need, but rendering them server-side using Node.js is VERY fragile. node.js is new and fairly unstable and its package management (exports...) requires lots of hacks for things to work properly.
  3. Google Closure Templates: these compile down to JS and Java and have a lot of the features I want. Unfortunately, browsing the Google groups, it looks like lots of basic features are missing (such as ability to loop over associative arrays) and the documentation for making your own plugins is very sparse and painful looking. Moreover, I can't tell who in the online community is using it, Google isn't accepting open source contributions for it, and they don't have the bandwidth to release new features.
  4. isotope: write templates in JS and use Johnson, a Ruby wrapper for the Mozilla SpiderMonkey JS runtime, to render those templates server side. Seems promising, but the project hasn't had commits in over 6 months.
  5. Liquid with Liquid.js: the Liquid templating language looks superb, but the liquid.js project seems to be untested (no testing in IE!), has no documentation, it's not clear if anyone uses it, and it hasn't been updated in a while.

Upvotes: 24

Views: 7321

Answers (3)

Yevgeniy Brikman
Yevgeniy Brikman

Reputation: 9361

We ended up picking dust.js. Check out Leaving JSPs in the dust and The client-side templating throwdown for more info.

Upvotes: 1

Raynos
Raynos

Reputation: 169383

Use EJS. It's pretty much got all the features you ask.

It can be used with express.js out of the box and it works nicely on the client.

As a bonus I would use backbone.js to do MVC on the client & server.

Of course this does rely on node.js. I feel that using express, now & backbone allows you a lot of stable control with node.js. Not to mention that SSJS is simply awesome and that code re-use is fantastic.

Upvotes: 3

Webthusiast
Webthusiast

Reputation: 1026

I would opt for XSLT (http://www.w3schools.com/xsl/xsl_client.asp)

Upvotes: -1

Related Questions