So exiting to see the launch of Compose 1.40 :slig...
# compose-web
c
So exiting to see the launch of Compose 1.40 🙂 But I see that now the README and homepage focus on WASM compose. Does this mean that the existing HTML compose will not be the standard approach?
Also, the link to https://kotl.in/wasm-compose-example redirects to https://github.com/Kotlin/kotlin-wasm-examples , where there is no compose example.
h
The existing Compose html dom api won’t go away.
f
ah okay, looks like the old Compose for Web is now referred to as the "Compose HTML Library" https://github.com/JetBrains/compose-multiplatform/pull/2997
c
Does this mean that the new compose web(wasm) will have the same components as JVM/Native/Android? 😮
f
That's correct
Makes sense to rename the older Compose for Web since the API was so different from Compose UI
c
👍 Thats awesome
f
I do hope that the HTML-based Compose continues to stick around for a while, we have an app that we're just about to ship to production that uses it
especially since Wasm-GC requires an up-to-date web browser (which is not the case for certain web-based platforms, like Smart TVs)
o
Just want to confirm what was already concluded above: it's a renaming to clarify/emphasize the approach to develop a web app. Compose HTML is a library (based on compose runtime) with Composable HTML building blocks (same as it used to be). Compose for Web (k/wasm) will aim to share the most of the UI code with other platforms (android, ios, desktop), and it renders on Canvas.
b
Also, the link to https://kotl.in/wasm-compose-example redirects to https://github.com/Kotlin/kotlin-wasm-examples , where there is no compose example.
@CRamsan give it one more chance 😉