Wow π€©! @wasm.io just wrapped last week, and the first talk is already live π
Check out:
βTowards a Component Model 1.0β by @lukewagner.name
π
www.youtube.com/watch?v=qq0A...
#WebAssembly #Wasm #wasmio26 #ComponentModel
π₯ BREAKING π°: Kotlin Wasm Component Model support to debut at #hyperlight-wasm workshop during #wasmio26
Don't miss!
2026.wasm.io/sessions/han...
#Kotlin #Wasm #ComponentModel #HyperlightWasm
Check out a sample server using wasi-http built with our early #WebAssembly Component Model support in @Kotlin! π€©
github.com/Kotlin/sampl...
Still early, but very satisfying to see it working β¨
Give it a spin and share what you build π
#Wasm #Kotlin #ComponentModel
1/2π
When I use cargo component new to build a CLI component for Rust/Wasm/Wit, the cargo component build step will automatically translate a main function to .e.g. wasi:cli/run or println! statements to the according stream functions from the wasi world. With wasm-tools component wit I can even [β¦]
#ComponentModel next (of #WASI preview3/#WASIp3) really seems to be trying to end function-coloring as a problem. That's some Epic-grade end-game-boss raiding against computing runtimes.
Right now there are very few languages that seem on course for #wasm #ComponentModel. Rust is one. And I'm interested, clearly has a very amazing community.
But hot damn, it is really scary to read about.
iroh.computer/blog/async-r...
So curious which #wasm targeting programming languages are going to get #ComponentModel support first. There's a ton of languages out there! But not part to the user-assembleable world.