As usual. with live demo :wink: <https://twitter.c...
# compose-web
b
l
What am i missing here There is only android,desktop and ios on the sources, not web 🤔
I see, its on the shared build gradle
j
For me it is weird it is on shared
d
@spierce7 As WASM has proven viable then I imagine that makes JS Compose a low-value distraction by comparison. WASM support being common in browsers isn't far away, JetBrains are doing the right thing by getting ahead of the curve here IMO. Makes sense to still support HTML DOM as y covers different use cases but if you had to pick 2 out of 3 tech foundations I think WASM+HTML is right.
s
It just means we're starting over from a compiler standpoint. It took js years to get proper incremental compilation and debugging.
k
gpt says WASM is already supported by all mainstream browsers.. Is there a roadmap on it's development and standardisation ? or is there a roadmap for Compose Web and WASM integration ? is this WIP right now ?
c
kotlin wasm support needs wasmgc which is not widely supported
h
Non-acill characters do not display properly and will become 口
d
@huachang It should be a matter of typeface only. See chrishatton.org showing Chinese character rendering in Compose Web (JS, but same)