WebAssembly

Gate project: portable program state migration using WebAssembly.

<h1 id="understanding-wasm">understanding wasm</h1> <h2 id="part-2-whence-wasm">part 2: whence wasm</h2> <p>“Write once, run anywhere” is a great sales pitch. It grabs your attention. It’s pithy! It invites the reader to fill in the blanks of “who is writing what, where is it going, and how does it get there” with the answer that most appeals to them. This was Java’s sales pitch. WebAssembly seems to have the same goal. Given that Java still exists, why do we need WebAssembly? What makes them different?</p>

Understanding Wasm, Part 2: Write once, run anywhere. If the Java Virtual Machine exists, why do we need WebAssembly?