Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to SafariWhen comparing swig 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 swig is ranked 14th. The most important reason people chose Dust.js is:
Easily extendable using filters and helpers. Can consume any public API.
Question Ranking
Pros
Pro Works both on the client and on the server
Available for node.js and major web browsers
Pro Does not hide HTML
Swig does not abstract HTML syntax from you (like e.g. Jade does) giving a certain filling of control over the markup.
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 No updates for at least 6 months
Swig has not received any new commits since June 25 2015.
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.
