qemu_esp32 VS ulisp

Straight up UDP streaming might be faster, since there's no error detection involved. Something to consider here: https://github.com/Ebiroll/qemu_esp32/tree/master/examples/19_udp

Back in the day we used to have to break out the UV EPROM eraser which would take about 40 minutes to erase and then do the program and test cycle so to avoid that we would use an emulator and do the initial testing on that. Not sure how suitable it is but there are ways to simulator an ESP32 CPU also: https://github.com/Ebiroll/qemu_esp32

I love his projects too. He's also the creator of uLisp.

http://www.ulisp.com/

Not CL, but there is ulisp (http://www.ulisp.com/) for microcontrollers, supposed to be really tiny, and there is Carp (https://github.com/carp-lang/Carp) which is without a GC so seems suitable for real-time stuff.

There's also ulisp (for Arduino projects etc.): http://www.ulisp.com/

This is larger, because there are functions for accessing peripherals, and the core is more standard lispy with 'caadr' et.al., and it has a compacting GC, so images can be saved as a compact blob.

You might consider uLisp, it's very Common Lispy for the memory constraints given (sans macros and splicing quote). And you can still connect to it and save an image. I've tried it and it works well enough. Here is the homepage.

Agreed - the interactivity is good. Lisp is close (have you seen http://www.ulisp.com/ - I can't believe they got into into that small a target!). Python is ok, but for some reason I don't use the REPL in the same way I do in Forth - I think calling functions is just harder somehow. Mostly is exploring valves from the Python REPL.