Hello, I'd like to find out in some more detail how you intend to solve the lightweight process problem (or have you solved it already?). As far as I can see, an erlisp process is mapped directly to a SBCL thread, which in turn is a wrapper for an OS thread. This is exactly what erlang tries to get away from and what the erlang VM is geared to do differently. --Sriram.