OTP and Gleam
summary
Gleam implements OTP as two packages on the BEAM, reusing primitives like spawn, link, monitor and wrapping them for Gleam ergonomics, while solving type safety by encoding message identity with typed message subjects (a from/subject pattern) so PIDs carry allowed message types. Gen_server semantics are reproduced with explicit reply/state steps, and real-world evidence includes high‑performance HTTP servers (Mist and you) and production SaaS use, so Gleam OTP is Erlang-compatible and practical.
AI-written summary · about
chapters (12)
- 0:00OTP and Gleam intro
- 1:08What is OTP in BEAM
- 4:37OTP with Gleam
- 6:01Gleam OTP goals
- 8:29Reusing Erlang OTP APIs
- 9:32gen_server challenges in Gleam
- 10:57OTP primitives in Gleam
- 13:45Typed message sending
- 15:11gen_server in Gleam
- 17:40Gleam OTP usability
- 18:43Summary and future
- 19:28Q&A: gen_server replies
related talks
01h 02mYour next favorite programming language: Gleam
38mA Code Centric Journey Into the Gleam Language
34mInterview with Louis Pilfold on Elixir Gleam
47mPurescript on the BEAM; Typed OTP for greatness
41mEnd-to-end Purescript with Erlang/OTP
42mConcurrency Oriented Software
39mFunctional Concepts in Elixir
37mElixir - functional, concurrent, distributed programming