Based on Erlang
A team at Erickson, including Joe Armstrong, was building applications to work with phone switches. Erlang, the movie,[2] tells this story. These telecom programs had to be extremely reliable, with real-time performance, and excellent concurrency. Because of Joe’s experience with Prolog, they wanted a language that would work in a declarative style. They quickly ruled out languages like C and Smalltalk because they weren’t declarative or expressive enough for the problems Erickson was solving. They also ruled out existing functional languages like Prolog and ML because those languages didn’t have the support for concurrency or low-level constructs for dealing with the bits that often showed up in hardware problems. Reluctantly, ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access