Erlang 101 - Processes & Parallelization

I’ve only watched the first 7 minutes but already enjoying it. Was nice seeing this comment about Joe from Alan Kay too:

What makes Elixir StackOverflow’s #4 most-loved language? What makes Erlang and Elixir StackOverflow’s #3 and #4 best-paid languages? How did WhatsApp scale to billions of users with just dozens of Erlang engineers? What’s so special about Erlang that it powers CouchDB and RabbitMQ? Why are multi-billion-dollar corporations like Bet365 and Klarna built on Erlang? Why do PepsiCo,,, Boston’s MBTA, and Discord all rely on Elixir? Why was Elixir chosen to power a bank? Why does Cisco ship 2 million Erlang devices each year? Why is Erlang used to control 90% of Internet traffic?

This video explores why Ericsson created Erlang to solve problems unique to the telecom industry in the 1980s and how the unique concurrency model it evolved (an functional programming implementation of the actor model) solves scalability and reliability/fault-tolerance problems confronting software engineers today who can’t unlock the full power of modern multi-core CPUs due to the dangers of shared, mutable state, which forces languages like Python and Ruby to use global interpreter locks (GILs) and languages like Node and JavaScript to use a single-threaded event loop, surrendering the ability to run their programs in a truly parallel way on more than one CPU core or more than one computer.

We’ll do some basic Erlang programming to demonstrate how Erlang’s lightweight processes and message-passing work and how process isolation and shared-nothing memory enables Erlang and Elixir programs to effortlessly and safely scale across all CPU cores and across computer clusters.


Alan and Joe did some keynotes together. They seemed to enjoy bashing C++ & Java together.