I'm thinking on starting a project with compose ht...
# compose-web
g
I'm thinking on starting a project with compose html. Just want to confirm first if there are any plans to stop the support and development in the perceivable future?
c
They have confirmed multiple times that they plan to do maintenance releases to ensure it keeps working for the foreseeable future, but they are concentrating their efforts on the Canvas-based/WASM approach, so we shouldn't expect new features. If you want more features (Markdown support, navigation, project generator…), I recommend taking a look at #kobweb
g
Thanks @CLOVIS
f
I also recommend #kobweb. I am using it for my app and it works really well
a
I am still surprised that they are compared to each other. Compose naturally fits very well with the dom and canvas/WASM has a completely different use case. They are almost orthogonal to each other
c
Yes, that's why JB is providing both. However, concepts like modifiers just don't work where you don't control the entire render pipeline, so Compose HTML cannot share composables with the other platforms. I'm not surprised most of their efforts go towards the multiplatform-friendly solution.
I'm glad Compose HTML has everything necessary for us to build other libraries on top of :)
d
We will continue to support both stable Compose Web HTML and the new experimental Canvas (WASM) target
d
@CLOVIS and @Filip Wiesner thank you so much for your Kobweb support!
s
@Dima Avdeev 👍 Are there any plans to compile compose html using wasm instead of kotlin/js ? Latest 1.9.0-beta wasm compiler has some amazing improvements in footprint and might be beneficial to normal dom based applications too.
d
@suresh I think for now it is better to leave Compose HTML with Kotlin JS. At first - because Compose HTML is already stable, and Kotlin WASM is an experimental target. At second - to operate HTML DOM, anyways needs to use JS