That s not what I think we were expecting based on previous convo s I thought < C01F2HV7868|compose web> was to be renamed to ` compose html` because of its historical content Then a shiny new < C01F2HV7868|compose web> created to be filled only with talk of our bright new WASM future sparkles wasm This seemed like a reasonable plan < hhariri>

See the reason why we don t split this channel into `compose html` and `compose web` <https kotlinlang slack com archives C0B8W32VA p1685015555505999 thread ts=1684520223 300899 amp cid=C0B8W32VA|here>

That s not what I think we were expecting based on previous kotlinlang #compose-web

Channels

100daysofcode

androidgithubprojects

cincinnati-user-group

competitive-programming

event21-community-content

java-to-kotlin-refactoring

jvm-ir-backend-feedback

kotlin-multiplatform-contest

kotlinultimatechallenge

myndocs-oauth2-server

naming

navigation-architecture-component

practical-functional-programming

proguard

prozis-android-backup

refactoring-to-kotlin

russian-kotlinasfirst

skia-wasm-interop-temp

stayhungrystayfoolish

swagger-gradle-codegen

tricity-kotlin-user-group

Title

darkmoon_uk

05/25/2023, 3:44 AM

That's not what I think we were expecting based on previous convo's... I thought #compose-web was to be renamed to

#compose-html

because of its historical content. Then a shiny new #compose-web created, to be filled only with talk of our bright new WASM future ✨ :wasm: This seemed like a reasonable plan... @hhariri?

Igor Demin

05/26/2023, 9:41 AM

See the reason why we don't split this channel into

compose-html

and

compose-web

here.

mohamed rejeb

05/26/2023, 10:11 AM

Also, we could be using

compose-html

and

compose-web

together by embedding a canvas powered by

compose-web

into a

compose-html

website so they are not separated. It's the same as using compose-ios with uikit interop

2 Views

#compose-web Join Slack