Wasm2Mpy: Compiling WASM to MicroPython so it can run on Raspberrys

I feel like this project is a classic example of the README missing a "Why?" section. Not to justify the project, it just makes it hard to evaluate without understanding why they choose implementing a transpiler rather than an embedded WASM VM. Or why not transpile to native assembly? I'm sure they have good reasons but they aren't listed here.

What would be the recommendation to run on ESP32?<p><a href="https:&#x2F;&#x2F;github.com&#x2F;wasm3&#x2F;wasm3">https:&#x2F;&#x2F;github.com&#x2F;wasm3&#x2F;wasm3</a>? <a href="https:&#x2F;&#x2F;github.com&#x2F;espressif&#x2F;esp-wasmachine">https:&#x2F;&#x2F;github.com&#x2F;espressif&#x2F;esp-wasmachine</a> ? <a href="https:&#x2F;&#x2F;github.com&#x2F;bytecodealliance&#x2F;wasm-micro-runtime&#x2F;tree&#x2F;main">https:&#x2F;&#x2F;github.com&#x2F;bytecodealliance&#x2F;wasm-micro-runtime&#x2F;tree&#x2F;...</a> ? <a href="https:&#x2F;&#x2F;github.com&#x2F;TOPLLab&#x2F;WARDuino">https:&#x2F;&#x2F;github.com&#x2F;TOPLLab&#x2F;WARDuino</a> ?

Can we have python compiled to wasm compiled to python compiled to wasm compiled to python - just for obfuscation reasons?

Author here, ready to answer any questions.

A great way to allow code created in another language to be compiled to a MicroPython module and then run in a MicroPython environment.<p>These .mpy files are dynamically loaded into MicroPython using a regular python import.