When comparing Kweb vs Hapi, the Slant community recommends Hapi for most people. In the question“What are the best backend web frameworks?” Hapi is ranked 27th while Kweb is ranked 46th. The most important reason people chose Hapi is:
Hapi was developed and is still being used by Walmart. Being backed by such a major company means that it will not lose support any time soon and most importantly it's being developed by professionals and that you will always get support for it.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro No need to deal with complex JavaScript toolchain
With Kweb you work in Kotlin from the server, using your favorite Kotlin/Java tools. Kweb integrates and supports popular JavaScript frameworks like Semantic UI. No need to worry about WebPack, cross-compilation, ES6/ES7/React/Angular etc.
Pro Automatic server-side rendering to accelerate initial page render
Pro Handles state end-to-end, bind the DOM directly to DB state and it will stay in sync automatically
Pro Written in Kotlin, a modern, powerful, and fast-growing programming language
Pro Automates communication between browser and server
Pro Backed by a major corporation
Hapi was developed and is still being used by Walmart. Being backed by such a major company means that it will not lose support any time soon and most importantly it's being developed by professionals and that you will always get support for it.
Pro Consistency across applications
Hapi's philosophy is that configuration is more important than code. This is especially useful for very large teams because it helps developers maintain consistency and reusability throughout their code.
Cons
Con Not yet 1.0.0, still in beta and under active development
Con Requires too much boilerplate
Hapi seems to be made with large applications in mind. The sheer amount of boilerplate code it requires is simply not practical for a small web app. This also means that there are few examples of Hapi applications around for beginners to learn from.