wat-js VS pico-engine

Well Forth is possibly the most minimal VM over a platform, as evidenced by openfirmware.

It does have problems scaling though, in that if you've seen one Forth, you've seen one Forth ie. The variations required to fit a platform make them semi-incompatible.

That's not to say that a more lispy Forth wouldn't be useful though, in that a concatenative syntax allows us to pass custom datastructures around like APL, and CPS (delimited continuations with lexically scoped dynamic binding would come from the lisp side (see https://github.com/manuel/wat-js).

Memory management in Forth can handle multiple memory types eg. https://flashforth.com/ so adding something like ref counting (https://github.com/zigalenarcic/minilisp/blob/main/main.c) to handle the dynamic list side of things might mesh well.

In any case, if you're looking for a self hosting lisp that runs on bare metal, https://github.com/attila-lendvai/maru has been out for a few years.

https://github.com/manuel/wat-js

If you have delimited continuations then you can construct coroutines/threads/await/async, promises etc.

I guess that this might be suitable for many scenarios thanks to nodejs, but the runtimes it relies on are not exactly small.

The article is quite thorough and I enjoyed it as it reminded me of my forays in the domain. One nook in this domain, I never managed to investigate in the depth I would like is the Kinetic Rules Language [0] which makes the connection to complex event processing more pronounced.

CEP is not trendy, which is probably because of history and traditional implementations but I think it deserves a good look.

[0] https://github.com/Picolab/pico-engine is an implementation of the KRL