@neauoire Personally, I find a 10-20 second build quite snappy and under a minute (for bigger stuff) tolerable.

Total and strong agreement, though, that a rapid modify-build-test cycle is a huuuuge productivity (and just quality of life) win and well worth optimizing around.

For embedded development, this has also always meant "invest in a fast and hands-free way to shoot the new build down to the hardware", because nobody has time to spend their life swapping sdcards and suchlike.

@neauoire exactly why i like interpreted languages— iteration speed. i’m more mad scientist than anything.

@neauoire But that means you're trading the developer's time for the user's time in the long run.

@neauoire technically UXN is interpreted, it's compiled to a bytecode the vm can interpret.

Technically all compiled languages ASM are interpreted by the CPU before running. So I guess its a moot point. :)

use what brings you joy!

@neauoire I recently developed an RP2040 firmware (pretty good size, too) in MicroPython, then eventually ported the finished result to the C SDK. Partly for iterative ease, partly to see if I could get away with performance and feature set (very nearly).

@neauoire somewhat related story, today I started toying around with a game engine idea, after hours of tutorials and videos I remembered your wiki page about ASI C. It’s by far the most simple and to the point information on how to start with C and SDL2 so thanks for that!

@neauoire I use supetcollider for music because I can live program iterations listening in layers, stoping starting dynamic synth engines on n number of servers. Compile?