I see a focus on webassembly in the browser. But f...

# webassembly

[Arjan van Wieringen]

I see a focus on webassembly in the browser. But for me the greatest benefit is portability. So being able to create WASM workloads for K8s for instance. Will this also be in scope for Kotlin/Wasm?

[ephemient]

https://kotlinlang.slack.com/archives/C0B8RC352/p1679903481794519 is already possible

[darkmoon_uk]

Genuinely curious; how is WASM for K8s much more portable than, say, setting up CI to build a Jetty image containing your Kotlin App as a JVM WAR file?

[darkmoon_uk]

Is it just the promise of fewer 'moving parts' in the process?

[Chad Lung]

The

intro video▾

recently posted mentioned experimental Docker support for WASM. I'm planning to check that out this weekend. I too am curious to see how this will be utilized with Docker, K8s, etc.

[Arjan van Wieringen]

@darkmoon_uk well, you’re right in a way of course. However, you can run WASM on more places. The K8s benefit is that you don’t have a Docker image anymore. Pipeline is just compiling the WASM. The Kubelet will just run the wasm file. Sizes are smaller, complexity is lower.

[Trevor Stone]

I believe WASM also is cross-architecture, so you don't need multiple releases if you have some devices running arm and some x86

[sdeleuze]

Exactly, you will directly ship the Wasm (WASI) artifact instead of the OS and CPU specific container.

It is not just about portability, but also of the capability to start in a few microseconds, 100x size reduction and other magnitude of order changes.