When comparing JQuery vs Webix, the Slant community recommends Webix for most people. In the question“What are the best JavaScript libraries for building a UI?” Webix is ranked 8th while JQuery is ranked 18th. The most important reason people chose Webix is:
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.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro Easy to use
Much easier to use than traditional JavaScript. Allows a lot of features and function to be completed with less lines of code.
Pro Cross-browser support
jQuery works on all modern browsers, although there may be some issues with old versions of each browser.
Pro Strong community
The open source community has really embraced jQuery and it has many readily available plugins to help speed up the development process. In addition to this, it has great documentation and tutorials
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 It is not a framework, but rather a library.
Frameworks allow you to handle page routing, authentication, and services. jQuery is not a framework, but rather a library of DOM tools for websites.
e.g.: You cannot write page routing logic within jQuery.
Con Script download
As opposed to just using raw JavaScript, users will (automatically) download the jQuery script to their local computers in order for it to work. This results in more overhead on the initial page visit, regardless of how lightweight the framework is.
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.