When comparing Kweb vs Pyramid, the Slant community recommends Pyramid for most people. In the question“What are the best backend web frameworks?” Pyramid is ranked 15th while Kweb is ranked 46th. The most important reason people chose Pyramid is:
Pyramid can be used for creating small applications quickly and easily, but it also powers up large enterprise-scale applications such as Dropbox.
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 Very flexible
Pyramid can be used for creating small applications quickly and easily, but it also powers up large enterprise-scale applications such as Dropbox.
Pro Persistence agnostic
Either NoSQL and SQL (including SQLAlchemy plugin).
Pro Comes with security included
Includes authorization and authentication with multiple backends.
Cons
Con Not yet 1.0.0, still in beta and under active development
Con The great number of options it offers can become intimidating
One of Pyramid's greatest drawbacks is that it requires a lot of set up in the beginning of a project. This can feel overwhelming and can keep people away from using it.