Resistance to Erlang

David Hopwood writes:
> To correct a minor technical point, Erlang supports asynchronous message passing.
> The pi calculus uses synchronous message passing, which is a quite different
> model.
Actually there are asynchronous variants of the pi-calculus
(Boudol, Honda-Tokoro).
Another difference is that the pi-calculus allows dynamic creation
of communication channels. Processes can send *and receive* on any
channel they know, which is an implementor's nightmare. For most
practical purposes, make_ref() and selective receive patterns
provide the same functionality in Erlang. Having receive queues as
first-class values could be interesting, through.
-- Pascal Brisset