PS. I dont mean to be critical about Erlang, I just dont think the article addresses the question in its title.
PS. I dont mean to be critical about Erlang, I just dont think the article addresses the question in its title.
If on the other hand you mean passing data between completely isolated active entities (processes) that get scheduled for execution independently based on available CPU cores, I/O operations, receiver mailbox size... Then you need an multitasking operating system, which is in fact what the Erlang VM is.
Or you can use Python multiprocessing on Linux, or Scala actors, or Haskell actors, or Clojure agents...
The short version: apparently you can do this in other languages, but erlang (and possibly other languages) have this concurrency baked-in much better.
p.s. also worth mentioning RabbitMQ on the list of famous erlang projects