Dust.js vs XSLT in-browser implementation

Easily extendable using filters and helpers. Can consume any public API.

Dust.js compiles its templates to plain old javascript, and since javascript files are cacheable, that essentially means your templates can be cached at the client side.

Since Dust's templates are written in JS, there's nothing stopping you from running the same DustJS code both on the client as well as server side (if it supports V8/Rhino JS engine).

Dust.js is quite easy to begin with, thanks to it's powerful interactive tutorial.

I.e. apply one template on top of another.

With ability to split feature implementation apart from main codebase, development became quite more manageable. Example: for data of particular type you could define own rendering or render refine rules; pipelining allows incrementally change UI by adding/removing elements depend of parameters, data values, previously rendered content.

Only template engine which utilizes multithreading.

In some browsers(IE) XSLT during load is compiled into DLL. In others pre-loaded template allows to skip recurring parsing .

XML when stored, saved outside of JS heap, capable to work with amount of data 100x larger of JSON.

Supported in all browsers, starting from IE5.

XSLT is available as in browser as on server side via various libs including highly optimized for CPU.