Skip to content

Details

The purpose of WebAssembly (Wasm) is to enable the JavaScript engine of a web browser to execute page scripts nearly as fast as native machine code. But this is not a full replacement for JavaScript; rather, Wasm is only intended for performance-critical portions of page scripts. Wasm code runs in the same sandbox as regular script code, but only regular scripts have direct access to the DOM tree.

Agenda:

18.30
Let's build Game of Life in Wasm (EN)
Tomáš Koutský

At first, we will briefly look at Wasm programming language itself,
understand its memory model and how boundaries between it and JavaScript work. Using this knowledge we will move on to the second part where we'll walk through Game of Life implementation in Rust.
Why Rust? Amongst other great features, it can be easily compiled to Wasm while allowing much better development ergonomics and has one of the best Wasm tooling. In the end, we'll look at one of the exciting new additions to Wasm - threads!

19.15
How we ditched Javascript for WebAssembly (EN)
Jakub Mirovský, Avocode

Well we didn’t. WebAssembly is used as a buzzword in the tech world and is being talked about like something to replace Javascript. We decided to use WebAssembly for the performance-heavy parts of Avocode (like our rendering engine) and in doing so we came across some difficulties that we had to understand and overcome. How did we manage to do it? What did we learn? And what do we want to do with it in the future?

Our sponsor:

Price f(x) is a modular SaaS pricing solution, based on the latest in native cloud architecture. Perfect for enterprises of any size, we serve over 80 global clients like Robert Bosch & Schneider Electric, across a variety of industries.

Related topics

You may also like