Frequently Asked Questions¶
Won’t Kweb be slow relative to client-side web frameworks?¶
No, Kweb’s immediate events allow you to avoid any server communication delay by responding immediately to DOM-modifying events. This should address the majority of scenarios where a server-driven approach might otherwise be sluggish.
What’s the difference between Kweb and Vaadin?¶
Of all web frameworks we’re aware of, Vaadin is the closest in design and philosophy to Kweb. In many ways Kweb is a philosophical descendant of Vaadin. This makes Vaadin one of the most useful frameworks to compare Kweb to, as there are also very important differences:
- Kweb is far more lightweight than Vaadin. At the time of writing, kwebio/core is about 4,351 lines of code, while vaadin/framework is currently 502,398 lines of code, almost a 100:1 ratio!
- Vaadin doesn’t have any equivalent feature to Kweb’s immediate events, which has led to frequent complaints of sluggishness from Vaadin users because a server round-trip is required to update the DOM.
- Vaadin brought a more desktop-style of user interface to the web browser, but since then we’ve realized that users generally prefer their websites to look like websites.
- Kweb was built natively for Kotlin, and takes advantage of all of its language features like coroutines and the flexible DSL-like syntax. Because of this Kweb code can be a lot more concise, without sacrificing readability.
- In Vaadin’s favor, it has been a commercial product since 2006, it is extremely mature and has a vast developer ecosystem, while Kweb is still pre-1.0.
Is there a larger working example?¶
Yes, here is a simple todo list implementation which demonstrates many of Kweb’s features.