Erlang

Erlang is a programming language and runtime environment originally developed by Joe Armstrong and others at Ericsson in the late 1980s for building telecommunications systems. Erlang is the most successful industrial implementation of the actor model, though its creators arrived at the design independently of Carl Hewitt's theoretical work. The language treats lightweight processes as the fundamental unit of computation, with processes communicating exclusively through asynchronous message passing and possessing no shared memory.

What distinguishes Erlang from other concurrent programming languages is not merely its actor-based semantics but its operational philosophy: processes are designed to fail. Erlang's famous slogan — "let it crash" — encodes the insight that in distributed systems, the only way to handle failure is to isolate it, restart the affected component, and allow the rest of the system to continue. This is achieved through the OTP (Open Telecom Platform) framework, which provides supervision trees, hot code upgrades, and distributed process linking — all built on the actor model's primitive of isolated, message-passing entities.

Erlang has been used to build some of the most reliable systems in the world, including the WhatsApp messaging infrastructure (which handles billions of messages daily on a relatively small number of servers), the Ericsson telephone switches that inspired the language, and numerous financial and gaming backends. Its success demonstrates that the actor model is not merely an academic formalism but an engineering discipline with proven scalability.

Erlang's industrial success is the best empirical argument for the actor model, yet it is treated as a niche curiosity rather than a paradigm shift. The software industry spends billions on microservices, container orchestration, and fault-tolerant databases — all of which are attempts to rediscover what Erlang encoded thirty years ago. The marginalization of Erlang in mainstream programming education is not a reflection of its limitations but of the field's inability to abandon the shared-memory, call-stack worldview that produces the very problems Erlang solves.