Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to SafariWhen comparing Inferno vs zUIx.js, the Slant community recommends Inferno for most people. In the question“What are the best React.js alternatives?” Inferno is ranked 9th while zUIx.js is ranked 23rd. The most important reason people chose Inferno is:
Use it however you want in a framework of your own custom design. When things change in the industry, swap things out instead of being locked in by someone else's design.
Question Ranking
Pros
Pro Modular
Use it however you want in a framework of your own custom design. When things change in the industry, swap things out instead of being locked in by someone else's design.
Pro Pretty light-weight
Inferno weighs in at 9kb gzipped, which is light-weight.
Pro Fast performance
Inferno is one of the fastest UI libraries around and widely considered the fastest.
Pro React compatability
Using the Inferno compatibility package ("inferno-compat"), Inferno can support the vast majority of React codebases.
Pro Ease of use
Requires only basic HTML/Javascript knowledge.
Pro In-browser bundler
Can pack assets and resources in the browser console with no need for any external tool.
Pro Component-based
Creating a component is just a matter of creating 3 small files (html, css, js).
Can share and load components across websites.
Pro Web Starter Project
If you like Node.js and automatic build system, the zuix-web-starter is a "blank" web project featuring LESS, Markdown, Minify, Eslint checks, automatic bundling, PWA optimizations and much more.
Pro Lazy-loading
Built-in lazy loading feature. Almost transparent.
Pro Templates
With automatic fields mapping (data binding).
Pro jQuery alike helper
Built-in DOM helper. Basically a lite subset of jQuery.
Pro Examples
The zKit site is a collection of example components ready to use as-is or as a base for creating your own components.
Cons
Con Some React components may not work with Inferno
Inferno and React have different public and private APIs. If 3rd party components use a private API then it's almost certainly going to break when you use it with Inferno.
Once React Fiber is implemented, even libraries that are currently working will break and will not be supported by Inferno.
Con Not very popular
Which can hinder one's opinion of its future, but the future of all "frameworks" is to break things into smaller pieces, so inferno very well might get used by the big names in the future.
