How does a WebAssembly runtime work anyways?

WebAssembly is an up and coming technology thats seen quite some hype around it. The promise of being able to run C/C++ or even Rust code directly within your browser for near native speeds sounds amazing. But as of late there has been considerable effort to use wasm outside the web browser.

Currently WebAssembly in the web embedding so to say has reached some level of maturity.

I'll be diving deep into the anatomy of the WasmEdge runtime and discussing its internals and how it works, along with my experiences working with this incredibly cool project. We will be looking into a few select components, namely:

-The bytecode format and s-expressions.

-.wasm and .wat formats

-runtime internals

-plugins system(if time permits)

I'll also talk a bit about the current limitations of WebAssembly, what the nuances are amidst all the hype of WebAssembly and what the current ground reality is of this very new technology.

The contents of this talk can be fit into either a full length talk or even a lightning talk, depending on the depth I go in.