If Erlang is a perfect 10 (or not!) in the world of distributed,
concurrent, load-sharing networked interoperable (etc., etc.) software,
what does picolisp bring to the table? What can I do along these lines in
picolisp? Erlang allows a node to have thousands of "light' processes. How
does picolisp do this?


Reply via email to