When comparing Deku vs w2ui, the Slant community recommends Deku for most people. In the question“What are the best JavaScript libraries for building a UI?” Deku is ranked 9th while w2ui is ranked 11th. The most important reason people chose Deku is:
Functional approach.
Ranked in these QuestionsQuestion Ranking
Pros
Pro Functional
Functional approach.
Pro Server side rendering
Deku can render it's components and data server side, then it sends those components as HTML to the browser.
This ensures faster initial loading time and SEO friendliness out of the box, since it's indexed as any other static website by search engines.
Pro Easy to learn
Since Deku is very lightweight and has a rather small API, there's not much to learn. It's pretty easy to get started and build something with it.
Pro Can use JSX
Developers using Deku can choose to also use JSX if they want to. This is especially helpful for people who are moving from React to Deku.
Pro Good performance
Deku's diffing algorithm is considerably faster and performs better than most libraries. The dbmonster performance mini-app written in Deku renders roughly 16% faster than other libraries.
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.
Cons
Con No support for legacy browsers
Deku does not support legacy browsers, or relatively old browsers for that matter. They only support the latest versions of the major web browsers.
Con Not a lot of learning resources
Since it's a rather new library and has a small community, there are not many examples where you can learn from out there. There are also few guides and the documentation is not amazing and has some parts that should be covered better.