toit-color-tft VS toit

As an example, here's the driver for small TFT screens of the type that is built into the M5Stack. This is an SPI-attached device: https://github.com/toitware/toit-color-tft/blob/main/src/col...

If you just have an M5Stack Core2 and want to play with it, then you don't need to write a new driver though. Probably you want the examples from this package: https://pkg.toit.io/package/github.com%2Ftoitware%2Ftoit-m5s...

(The implementation of that package in the src directory is an example of using an I2C peripheral.)

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...