esp32-doom VS MicroPython

Since it looks to be built on the ESP32 platform, the answer is likely yes (but you'd need a display...) https://github.com/espressif/esp32-doom

I think actually there are a couple of DOOM ports for the platform.

My most pressing question is, can it play Doom?

There seems to be a port for ESP32 [0] and Arduino Nano does play it [1], so maybe?

[0]: https://github.com/espressif/esp32-doom

[1]: https://m5stack.hackster.io/naveenbskumar/yes-arduino-nano-e...

Perhaps try this: https://github.com/espressif/esp32-doom

should be fine, yeah

There is a port of DOOM for an ESP32, proving that it can be done, however I have added additional constraints on myself as follows:

Now all we need for DOOM everywhere is to make the memory management more portable. It's still difficult to port DOOM to microcontrollers like the ESP32 and ARM Cortex-M and RISC-V, which are easily fast enough to run it but which have much less RAM than a 90's PC (128-512K vs 4MB). But they can use external RAM via SPI which is very cheap for 4 or 8 MB, and while that is slower than 90's DRAM because of the serial protocol it should be good enough with a very simple cacheing strategy?

it's not an embeddable runtime like Lua

While it's true you can't have multiple MicroPython interpreters running concurrently (or at least not easily; it's not that the design makes this impossible, it's just that all in all MicroPython is fairly young and development focus has been put elsewhere), it is possible to embed MicroPython. Not completely out of the box, needs some glue code etc. See for example https://github.com/micropython/micropython/tree/master/ports....

It's obviously not directly comparable - each port will be different - but startup time is <50ms on an RP2040 (Cortex M0 @133MHz):

https://github.com/micropython/micropython/issues/8420

Yes, although MicroPython is focused on running on microcontrollers it can be useful if you want to reduce memory consumption, flash space and even startup time on servers.

The challenge is that MicroPython has many fewer standard libraries:

https://github.com/micropython/micropython/wiki/Standard-Lib...

And so many Python libraries targeting CPython won't work out-of-the box and you'll need to modify them or use alternatives that do work on the MicroPython subset.

I'll link to it because many people don't know a version of Python runs on microcontrollers:

https://micropython.org/

I'm personally working on something like this for the ESP32, but written on top of micropython [1]. A few things are written in C such as the display driver, but otherwise most things are in micropython. We chose the T-Watch 2020 V3 microphone variant as the platform [2].

Our objective is to build a modern PDA device via a mostly stand-alone watch that can be synced across devices (initially the Linux desktop). We want to achieve tasks that you might typically do on your desktop, focussed towards productivity.

We did consider a custom OS, but decided against it for a few reasons:

1. Allowing somebody else to handle basic OS stuff allows us to concentrate on what really matters, the higher level stuff on top.

2. Having multiple threads in micropython is super simple and we are able to run many active apps at the same time, rather than having to kill them off [3]. Our background apps can continuously interact with the network in the background.

3. Code written for micropython can be easily run on other Python-capable devices.

[1] https://micropython.org/

[2] https://lilygo.cc/products/t-watch-2020-v3

[3] https://tactility.one/#/application-lifecycle

tools/mpy_ld.py: https://github.com/micropython/micropython/blob/master/tools...

tools/mpy-tool.py lists opcodes: https://github.com/micropython/micropython/blob/master/tools...

Can the same be done with .pyc files; what are the advantages of MicroPython native modules?

Why does it need wasm2c?