Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to SafariWhen comparing Dust.js vs Webix, 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 Webix is ranked 13th. The most important reason people chose Dust.js is:
Easily extendable using filters and helpers. Can consume any public API.
Question Ranking
Pros
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.
Pro A lot of widgets
Webix is one of the most extensive UI component libraries, second only to Sencha ExtJS. Not only considering the number of widgets, but also the API methods for manipulating these widgets.
Pro Views can be constructed using JavaScript without HTML
The most common way of working with webix is to create a JSON configuration of your view in JavaScript. When you use TypeScript, you get complete typechecking and intellisense in your IDE.
Pro Seems to be quite stable
Even the most complicated GUIs are bug-free most of the time.
Pro Webix Jet
The webix Jet library adds all the required features for SPA development (routing, template loading, ...)
Pro Extremely simple to implement.
To get started is extremely simple. It has a low learning curve.
Pro Mature project
Regular updates and releases.
Pro Great support from the webix team
The company behind webix is really quick in answering any questions you have on their forum or via email.
Pro Awesome responsive material skins
Great design and icons pack.
Cons
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.
Con Commercial license
It's not free for commercial applications.
Con Not very popular
Not really a reason to not recommend it. But it has still a small user base. It deserves a lot more attention.
Con Not modular
The library is not modular (except for some additional more complex widgets). If you only need a few widgets, you still need to include the entire library.
