Wasm was designed to run applications written in compiled languages such as C/C++, Rust, Swift, etc. However, as Wasm gains popularity, there are increasing demands to run Wasm applications in scripting languages such as JavaScript, Python and Ruby. Compared with native interpreters (or dynamic compilers), Wasm offers benefits to both devs and ops. Dev: Wasm is a polyglot environment that supports mixing high-performance compiled languages and easy-to-use scripting languages. For example, with Wasm, devs can safely wrap Rust functions in a JS API. Op: Wasm is a sandbox with OS access. It can be managed as a standalone container or be embedded in a host. Native scripting language VMs need to be wrapped in other runtimes (eg node) and Docker containers. Wasm can achieve significant savings in computing resources. In this talk, Michael will discuss the approaches and latest progress of Wasm support of scripting languages, like JS, Python, and Ruby. He will cover language interoperability, ecosystem (eg packages and modules) support, and performance characteristics. Finally, Michael will also briefly discuss Wasm support status for popular managed languages such as Java and .Net.
Click here to view captioning/translation in the MeetingPlay platform!
