- <imgsrc="https://cdn.rawgit.com/simple-icons/simple-icons/develop/icons/raspberrypi.svg"width="18"height="18"/> Raspberry Pi, Orange Pi and other **SBC**s
- <imgsrc="https://cdn.rawgit.com/simple-icons/simple-icons/develop/icons/firefoxbrowser.svg"width="18"height="18"/><imgsrc="https://cdn.rawgit.com/simple-icons/simple-icons/develop/icons/googlechrome.svg"width="18"height="18"/><imgsrc="https://cdn.rawgit.com/simple-icons/simple-icons/develop/icons/safari.svg"width="18"height="18"/><imgsrc="https://cdn.rawgit.com/simple-icons/simple-icons/develop/icons/microsoftedge.svg"width="18"height="18"/> Browsers... yes, using WebAssembly itself!
@ -61,14 +61,14 @@ Minimum useful system requirements: **~64Kb** for code and **~10Kb** RAM
☑ Sign-extension operators
☑ Non-trapping float-to-int conversions
☑ Import/Export of Mutable Globals
☑ Structured execution tracing
☑ Self-hosting
☑ Gas metering
☐ Multi-value
☐ Bulk memory operations
☐ Reference types
☐ Bulk memory operations
☐ Tail call optimization
☐ Fixed-width SIMD
## Motivation
@ -76,7 +76,7 @@ Minimum useful system requirements: **~64Kb** for code and **~10Kb** RAM
In many situations, speed is not the main concern. Runtime executable size, code density, memory usage, startup latency can be all improved with the interpreter approach. Portability and security are much easier to achieve and maintain. Additionally, development impedance is much lower. A simple library like Wasm3 is easy to compile and integrate into an existing project. (Wasm3 builds in a just few seconds). Finally, on some platforms (i.e. iOS and WebAssembly itself) you can't generate executable code pages in runtime, so JIT is unavailable.
**Why would you want to run WASM on microcontrollers?**
**Why would you want to run WASM on embedded devices?**
Wasm3 started as a research project and remains so by many means. Evaluating the engine in different environments is part of the research. Given that we have `Lua`, `JS`, `Python`, `Lisp`, `...` running on MCUs, `WebAssembly` is actually a promising alternative. It provides toolchain decoupling as well as a completely sandboxed, well-defined, predictable environment. Among practical use cases we can list `edge computing`, `scripting`, running `IoT rules`, `smart contracts`, etc.