>>38
I was a telco programmer, and 80% of my time went to problems caused by lost or corrupted inter-process messages. There are lots of things getting in the way of those messages: power outages, improper system shutdown by newb administrators, Oracle choking a cpu so bad it can't even read ethernet, abends/coredumps before a key progrma finishes procesing a message, and on and on. The more bullet-proof Erlang's message passing is the better. Extra hard drives for big queues and message logs are much cheaper than programmer time to track down some message that got lost 3 days before anybody noticed something was wrong.