w2c2 VS toit

For AOT, the simplest approach, that actually produces the fastest native code, is to naively translate WASM opcodes to C.

This is for example what W2C2 does: https://github.com/turbolent/w2c2

This uses [w2c2](https://github.com/turbolent/w2c2) to convert RustPython,

Using a modified version of the w2c2 wasm->C89 translator, I was able to run Rust code on 9front!

There's not much data in the performance section of the front-page readme of the repo, but the one bullet point there seems promising:

> Coremark 1.0: ~7% slower than native [0]

[0] https://github.com/turbolent/w2c2#performance

It uses toit, a high-level language, and is thus quite easy to learn. At the same time it's an order of magnitude faster than micropython.

We have been faced with the same question and decided to open-source pretty much all of our product (https://github.com/toitlang/toit).

I also really like MicroPython! Having said that, I have been working on an alternative to it for a number of years now -- primarily to provide a more robust and performant high-level alternative to C and Rust on the ESP32-family of chips:

https://github.com/toitlang/toit

I'd love to pick your brain and fully understand your experience with MicroPython. I've been doing programming languages for a number of years now, and I find that it is incredibly useful to understand what developers appreciate (and dislike) about the available stacks.

Thank you for the mention!

I have been working on the Toit language for the ESP32 for a number of years now -- and it has been an enjoyable challenge to build an open source stack capable of supporting live reloading on a micro-controller that can run for years on batteries.

https://github.com/toitlang/toit

We use it for some of our tools, so it's possible (and works nicely). Our LSP server was initially written in Toit: https://github.com/toitlang/toit/tree/master/tools/lsp/serve...