> How does WASM handle different architectures? The same way JavaScript or C#/Java do. It's a bytecode format (typically the first stage in today's JavaScript

> How does WASM handle different architectures? The same way JavaScript or C#/Java do. It's a bytecode format (typically the first stage in today's JavaScript engines is to turn into a bytecode), which the different engines then JIT for the OS and architecture they are running on. For more details on a couple different engine implementations, you may find the below of interest. - https://v8.dev/docs/wasm-compilation-pipeline https://v8.dev/docs/wasm-compilation-pipeline - https://hacks.mozilla.org/2020/10/a-new-backend-for-cranelift-part-1-instruction-selection/ https://hacks.mozilla.org/2020/10/a-new-backend-for-cranelif...