Hi, this is Patrick Dubroy and Mariano Guerra. You're getting this email because you purchased (or signed up for updates about) WebAssembly from the Ground Up. If you're no longer interested in these emails, no hard feelings — you can find an unsubscribe link at the bottom.
Greetings Wasm wizards,
We won't bury the lede — we just published a new blog post! It's called A WebAssembly interpreter:
In this post, we’re going to look at WebAssembly from another angle: we’re going to write an interpreter for Wasm from scratch. So, rather than executing the Wasm module with Node.js, we’re going to examine the instructions and evaluate them ourselves.
At the end of this post we will have a bytecode interpreter (or virtual machine) that can evaluate arithmetic and comparison expressions like 2 * 3 + 4 == 10.
If this sounds like fun, please do check it out! And, as always, we appreciate if you help us spread the word with shares/reposts, etc. 🙏
Wasm tidbits for November
- The W3C WebAssembly Community Group held a two-day, in-person meeting at the Google Munich office, followed by the Wasm Research Day. We were there for both events; it was great to meet some of the Wasm community in person.
- Did you know about the WebAssembly Discord? We didn't!
- Wasabi is a dynamic analysis framework for WebAssembly, created by Daniel Lehmann, who now works on Wasm on the V8 team.
- Chris Fallin is back with another epic blog post: Exceptions in Cranelift and Wasmtime. It's about "the odyssey I recently took to implement the Wasm exception-handling proposal in Wasmtime, the open-source WebAssembly engine for which I'm a core team member/maintainer, and its Cranelift compiler backend."
🍁 🍂
Until next time,
— Patrick and Mariano
0 comments