ancatrusca

ancatrusca

Sharing the latest BEAM There, Done That episode. This one is genuinely historic - the people who built the JAM and early BEAM, telling the story directly.

The hands-on detail that opens the episode: Mike looked at Joe Armstrong’s first 20 lines of C and said “this is awful.” He rewrote the inner loop, learned C while doing it, and got message passing down to six instructions. He was optimising the three numbers he’d identified as what determine whether a concurrent language lives or dies: process creation time, context switch time, and message copy time.

Why those three numbers matter: Mike measured it on real telecom workloads in the early 1980s - 70% of VM time was those operations, not application code. That measurement shaped every design choice that followed.

Why language-level concurrency was “obvious”: Not ideology - arithmetic. Unix process overhead made thousands of concurrent processes mathematically impossible on 16–64 MB machines. Language-owned scheduling was the only path.

The two-version rule: Still in the BEAM today. Björn was asked to remove it multiple times. He refused: unlimited module versions would let old code accumulate silently, wasting memory and causing surprises in production.

The person who always gets forgotten: Claes Wikström - who added distribution to the JAM, invented ETS tables, and prototyped Erlang’s binary syntax with Tony Roguel.

Showing Posts 1 to 1

AstonJ

AstonJ

Lovely to see Mike still around the BEAM world, and of course always great hearing @bjorng’s insights too :icon_biggrin:

@FrancescoC and @allenwyma great podcast/hosts as usual!

— All posts loaded —

Where Next? Top

Trending in Podcasts Top

PJUllrich
Praia Labs has the numbers on Phoenix version and Bandit adoption, Sobelow 0.15 is out, and there’s a new book, Elixir for Finance. We al...
New
PJUllrich
Peter announces Pushin.eu, a GitHub competitor hosted in the EU, written in Elixir. Other topics include Phoenix ships security patches s...
New
ancatrusca
Part one of two with the WhatsApp developer experience team. This episode covers scale and operations; part two covers tooling and types....
New
ancatrusca
AtomVM supports GenServer, maps, JSON, Erlang distribution, and via Popcorn - Phoenix LiveView on a microcontroller. No OS, a few hundred...
New
ancatrusca
Part two of two. Part one covered scale and operations; this one covers the tooling that keeps a large codebase navigable. The practical...
New

Other Trending Topics Top

mudasobwa
I am happy to introduce the very α version of the new programming language compiled to BEAM. Welcome Cure. It has literally three kille...
New
marciok
Hi there! We created Gust: A task orchestrator inspired by Airflow. For those who have never heard about Aiflow, it’s a Python-based wor...
New
jimsynz
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
Dmk
Xamal is a deployment tool for Elixir apps that deploys native releases to bare metal servers over SSH. It’s a port of GitHub - basecamp/...
New
Damirados
Hello everyone. After busy few months I am happy to announce v0.1.0 of Emerge & Solve. They are GUI (Emerge) and State management (S...
New
netoum
Corex is an accessible, unstyled UI component library for Phoenix that integrates Zag.js state machines using Vanilla JavaScript and Live...
New

We're in Beta

About us Mission Statement

Options

Thread Display Mode




Thread Preview

Skip Thread Previews