Fireside on making a typed language on the BEAM
summary
Claim is that it is practical to build a typed language on the BEAM rather than impossible and Gleam proves it by shipping a minimal 400 lines reimplementation of OTP primitives to expose a typeable abstraction. Caramel and Gleam use an FFI barrier to interoperate with existing Erlang libraries, emit Erlang with Dialyzer specs, and accept that hot code reloading and typing gen_server style dynamic dispatch remain hard problems to defer or wrap.
AI-written summary · about
chapters (10)
- 0:00Introductions and welcome
- 1:33Project origins and names
- 4:04Philosophy of naming and design
- 9:04Types and the BEAM ecosystem
- 17:21Dynamic code upgrades
- 20:09Gradual vs. strict typing
- 25:59Interoperability and FFI
- 30:57Practical implementation details
- 34:36Future goals and macros
- 37:51Closing thoughts and audience
related talks
34mErlang in the Browser
19mBAML: a new programming language for AI
32mA Practical Guide to Elixir Protocols
44mSome History of Functional Programming Languages
39mWhat if you could build production-ready RAG entirely in Elixir?
15mBAML - A New Programming Language for Building Agents
43mThe State of EVM Languages
01h 07m50,000 Lines of LLM Haskell: What Broke, What Held, and Letting Go