Language · 1986–now · Object Wave
Erlang / OTP
Let it crash, supervision trees, and nine-nines uptime. The telecom substrate that outlived every "modern" backend pitch.
Erlang stuck because fault tolerance at the process level was the right abstraction for switches and still is for WhatsApp-scale messaging. It never went mainstream because the syntax is a hiring filter and the JVM ate enterprise middleware. Admiration arrives late; adoption never left the niches that needed it.
Context
Everything became an object — until it didn't
Objects promised reuse; enterprises bought the promise in bulk. Java gave a portable runtime with real teeth. CORBA and UML-heavy processes gave vendors a decade of workshops. The survivors were the languages and platforms that outlived the methodology theater. The lesson — complexity sold as architecture burns cash — returns every decade with new branding.
Compare with
Related
Framework · 2014–now
Phoenix / LiveView
Real-time Elixir on the BEAM with HTML-over-the-wire before it was cool. Small but fiercely loyal community.
Language · 2019–now
Gleam
Erlang semantics with friendly syntax on the BEAM. The language your functional meetup loves and your employer has never heard of.
Language · 2011–now
Elixir
BEAM reliability with modern syntax. Phoenix and LiveView keep the torch for pragmatic functional web.