When comparing w2ui vs Inferno, the Slant community recommends w2ui for most people. In the question“What are the best JavaScript libraries for building a UI?” w2ui is ranked 11th while Inferno is ranked 15th. The most important reason people chose w2ui is:
Any component is well documented and have an easy API to access validation, dataloading and handling user events.
Ranked in these QuestionsQuestion Ranking
Pros
Pro Easy and clean API
Any component is well documented and have an easy API to access validation, dataloading and handling user events.
Pro Lots of components/widgets
Library contains UI components like Datagrids, Forms, Tabs, SideBars, Toolbars and more.
Pro Small library size
Only two files need to be included 1 .css and 1 .js, together they are only 365 kb.
regarding to amount of components it is very small.
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.
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.