That's not what I think we were expecting based on...
# compose-web
d
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?
🗿 1
👍🏾 1
👍🏻 2
mind blown 1
👍 14
i
See the reason why we don't split this channel into
compose-html
and
compose-web
here.
m
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
d
You can also combine Android XML and Android Compose widgets together, but conceptually they're very different and people asking about the first are likely looking for different answers than people asking about the second.
As an FYI, as someone mostly working in Compose HTML at this point, I'm starting to visit this channel less because most notifications tend to be about Compose Web these days. I'll ping that observation in the meta discussion too.