When comparing Json2html vs Dust.js, the Slant community recommends Dust.js for most people. In the question“What are the best JavaScript templating engines?” Dust.js is ranked 9th while Json2html is ranked 30th. The most important reason people chose Dust.js is:
Easily extendable using filters and helpers. Can consume any public API.
Ranked in these QuestionsQuestion Ranking
Pros
Pro Embedded jQuery Events
Allows for jQuery events to be embedded within the template when used on the client.
Pro No special template syntax to learn
Templates are JSON objects that can include javascript functions to render any complex logic.
Pro Portable to server and client
Templates are stored as JSON rather than HTML, easily ported to both client and server.
Pro Filters
Easily extendable using filters and helpers. Can consume any public API.
Pro Cache templates at the client side
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.
Pro Write once run anywhere
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).
Pro Interactive tutorial
Dust.js is quite easy to begin with, thanks to it's powerful interactive tutorial.
Cons
Con Templates can be hard to read
HTML structure for template replicated in JSON, can be hard to read.
Con There are no new releases
And apparently Linkedin will not support it more.
Con Not enough community support
Since the number of people currently using Dust.js is quite insignificant as compared to Mustache js and Handlebars, you're less likely to get your question answered or issue resolved if you start using it.