Erlang from the Outside
summary
Argues that Erlang already solved high‑scale concurrency decades ago but loses out to modern ecosystems because of poor onboarding and tooling; points to concrete fixes: rebar3 as a real build tool, hex for packages, and Elixir‑style tutorials that ease entry. Gives examples — WhatsApp as a success story, an npm‑style critique including CouchDB/Erlang ties, and a small “hello Joe” supervisor package — and claims these changes could increase adoption.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 2:50Ruby and JavaScript
- 5:23NPM
- 12:10Enterprise
- 15:38JavaScript
- 23:21Build system
- 25:27Package managers
- 26:21The Erlang community
- 27:54The Erlang ecosystem
- 28:35Being smug
- 30:00Why not be popular
- 30:56Haskell
- 32:34Node is popular
- 34:36A future for Erlang
- 37:25Conclusion
- 38:31Questions
related talks
23mWhat do you learn from not using Erlang?
01h 07mFireside Chat
39mUsing Nicer Programming Languages at Work
46mThings that Matter
19mPanel: Elixir Adoption
41m20+ Years in Tech: Things We Wish We Knew Sooner
45mFear and the Evolution of Languages
38mLearning Erlang and Elixir(..)Exercism and Advent of Code