My latest: Server-side #Wasm's Q4 release will provide a cleaner way to connect apps, followed by further improvements in early 2024. Will it be enough to convince skeptics? #WasmCon @RobustCloud @luke_wagner @hectaman #WASI https://www.techtarget.com/searchitoperations/news/366551352/Server-side-WebAssembly-takes-shape-but-faces-challenges

Looking for a little light travel reading on the way to #wasmcon?

Consider "Understanding WASM, part 3: You Are Here"! It's a deep dive on system interfaces: what they are, their history, and what WASI might mean for them.

https://www.neversaw.us/2023/09/04/understanding-wasm/part3/you-are-here/

#wasm #wasi #wasmcon

"Understanding WASM, part 3: You Are Here"

This is a deep dive into the history of virtualization technologies & techniques, in an attempt to frame where WebAssembly and WASI exist in that continuum.

https://www.neversaw.us/2023/09/04/understanding-wasm/part3/you-are-here/

#wasm #wasi

Running WASI binaries from your HTML using Web Components

https://runno.dev/articles/wasi-web-component

https://news.ycombinator.com/item?id=37287339

#WebAssembly #WASI #WebComponents

#Zellij terminal workspace.

https://zellij.dev

Extensible workspace #UI for the terminal using a #WebAssembly / #WASI based plugin system.

Seems WASI support in .NET will be (partly) postponed until .NET 9

The WASI tracking issue on Github now has Milestone set to 9.0.0 https://github.com/dotnet/runtime/issues/65895

This happened just after .NET 8 Preview 6 was released and I noticed when re-visiting my "Hello World" WASI, see https://henrikrxn.github.io/blog/Wasi-dotnet-8-preview-7/

#dotnet #wasi #webassembly #wasm

🔥⏲️ Fudge Sunday "South by Southwest Bound and Down" A look at South by Southwest® (SXSW®) from 2008 to 2024 🌮

#sxsw #panelpicker #sxswpanelpicker #sxsw2024 #artificialintelligence #ai #aiforgood #aiforall #aiandbusiness #wasm #wasi #bytecode #platformengineering #watsonx #devx #developerexperience #tacos #tacos #tacos #newsletter #newsletters

https://fudge.org/archive/south-by-southwest-bound-and-down/

Great to read about #ziglang 0.11 release, now with experimental support for #wasi threads! #wasm #webassembly
https://ziglang.org/download/0.11.0/release-notes.html

"The WASI OS" ← I'm giving a talk at WasmCon next month!

There's no WASI kernel yet, but as Unix teaches us, OS's can be about more than a single kernel. They can also be about a design philosophy, and about interfaces with many implementations. What's emerging in the #WASI OS, and what does it look like in practice with wasi-http and wasi-sockets?

https://wasmcon2023.sched.com/event/1Pm88

Today I get to revisit an old service - my very first WASI implementation where a Go app hosts a #wasi runtime that executes WASM scripts written in Rust. It dates back to v1 of https://wasmer.io. The goal is to try and make a Swift snippet compile to #wasm in a way that can run inside the runtime.

#WebAssembly: An Updated Roadmap for Developers

" This roadmap reflects changes occurring in standards within the WebAssembly Community Group (CG) and the #WASI Subgroup within the #W3C. This includes WebAssembly Core, WebAssembly Component Model, WASI (WebAssembly System Interface), and a number of WASI-based interfaces. "

https://bytecodealliance.org/articles/webassembly-the-updated-roadmap-for-developers

WebAssembly: An updated roadmap for developers
https://bytecodealliance.org/articles/webassembly-the-updated-roadmap-for-developers

Great news from the Bytecode Alliance on WASI & the Component model, even featuring a component registry!

#wasm #WebAssembly #WASI

@preslavrachev

1. Goroutines use "cooperative multitasking", they release control back to the scheduler when they are blocked or a certain amount of calls (what Erlang calls "reductions") passed since the last release.

2. You can do system calls only with #WASI which will be available only in #golang 1.21. You cannot do system calls from the browser (GOOS=js) for safety reasons. You can, however, use WebAPI to do network calls, and then you work with JS promises:

https://github.com/life4/gweb/blob/master/web/http_request.go#L21

1. Goroutines use "cooperative multitasking", they release control back to the scheduler when they are blocked or a certain amount of calls (what Erlang calls "reductions") passed since the last release.

2. You can do system calls only with #WASI (GOOS=wasip1) which will be available only in #golang 1.21. You cannot do system calls from the browser (GOOS=js) for safety reasons. You can, however, use WebAPI to do network calls, and then you work with JS promises:

https://github.com/life4/gweb/blob/master/web/http_request.go#L21

Playing around with #rust and #wasi is some of the most fun programming I’ve done in quite a while

#wasm

My slides for "A Small Update About TinyGo - GopherconEU 2023 Edition" are available here:
https://deadprogram.github.io/gopherconeu-2023

#gopherconeu #golang #wasi #webassembly #embedded #tinygo

Every #wasi step is a good step: WIT #vscode syntax highlighting as components begin to appear: https://github.com/bytecodealliance/vscode-wit/issues/7#issuecomment-1604764911

Exploring #WebAssembly outside the browser https://atamel.dev/posts/2023/06-20_explore_wasm_outside_browser/

#WASI #WASM

Looked into progress on WASI support in .NET 8 Preview 5

TL;DR Not much visible progress

https://henrikrxn.github.io/blog/Wasi-dotnet-8-preview-5/

#dotnet #webassembly #wasi

I wrote https://snarky.ca/wasi-support-for-cpython-june-2023/ to cover the state of #WASI support in #Python and where I hope it goes in the future