Gleam: Lean BEAM typing machine
summary
Gleam is a new statically typed language that compiles to the Erlang VM, interoperates with Erlang/Elixir packages via a simple FFI, and is implemented in Rust. It uses an ML-style static type system that gives compiler-generated to‑do lists for every place a change might break code, trading Dialyzer’s slowness for strict, fast checks. Benchmarks cited: BEAM servers handling 2 million connections and earlier tests spawning 20 million processes; Gleam is usable now but focuses next on LSP, docs and teaching materials.
AI-written summary · about
chapters (34)
- 0:00Introduction
- 0:53Why Erlang
- 1:38Telephone switch
- 3:37EachAppetit
- 4:15Felix Channels
- 5:04Ericsson
- 5:41concurrency
- 6:17sequential code
- 6:47Erlang threads
- 7:53Communication
- 9:02Garbage Collection
- 10:00Error Bulkheads
- 11:08Why Gleam
- 12:26Example
- 16:17Feedback loop
- 16:44ML languages
- 17:11Messenger
- 18:36Luminara
- 19:31How do they achieve this
- 20:35What are the advantages
- 22:00ML style error detection
- 22:47Examples
- 23:20Handling user inputs
- 24:18Video transcoding
- 25:19MLstyle error detection
- 26:36MLstyle offense programming
- 27:25MLstart type system
- 28:17Future of Gleam
- 29:08Language Server Protocol
- 29:51Documentation
- 30:08Elixir
- 30:53Exercise
- 31:57Gleams greatest strength
- 33:08Conclusion
related talks
01h 02mYour next favorite programming language: Gleam
25mTime, Hard Problems, other Hard Problems, Gleam
32mElixir for the rubyist
19mBridging the Gap with Gleam & Lustre
48mGetting to Know the Erlang Virtual Machine, the BEAM
42mIntroduction to Elixir for Rubyists
44mLFE - a lisp flavour on the Erlang VM
19mElixir – what it is and why is it amazing?