<https://github.com/Kotlin/kotlin-wasm-examples/tr...
# kobweb
s
https://github.com/Kotlin/kotlin-wasm-examples/tree/main/compose-imageviewer#compose-multiplatform-for-web:~:te[…]eb%20is%20based%20on%20Kotlin/Wasm - Since compose web is now based on kotlin/wasm, do you see any impact to compose dom APIs or kobweb going forward? I hope going forward, JB folks will actively maintain the existing compose dom/css libraries 🙂
d
For now, I'm assuming they will. I pinged the team in the #compose-web channel so hopefully we'll confirm by next week. Otherwise, I left this comment on Reddit yesterday: https://www.reddit.com/r/Kotlin/comments/12kauzh/jetbrains_compose_is_now_compose_multiplatform/jg48twa and I haven't changed my opinion yet. There's a chance this can push Kobweb up from a nice to have library to a must have framework for this space, since I've been spending a bunch of time filling in API gaps the JB team has so far not attempted to finish, and maybe now they're signaling they may not do so for a lot longer. Interesting times!
So full steam ahead on Kobweb