I agree with "With kweb we have to mutate the DOM ourselves”, it’s likely that someone will build some kind of component-based architecture on top of the current kweb low-level, to help organize state and code. Unlike with React though, we get all of the power, tools, and type safety of kotlin when we do it. We also don’t have to worry about client-server communication too much, whereas with React it’s a fundamental part of your app architecture.