Adopting Gleam the Boring Way
summary
Argues incremental adoption of Gleam works and is low-risk: Gleam compiles to Erlang and JavaScript source so packages include runnable Erlang/JS, FFI lets Gleam call Elixir/Erlang and vice versa, and a Mix PR already enables full Gleam support used in one real codebase. Demonstrates a persistent array library Ivy that interoperates with Elixir, frontend integration via Lustre with web components, form-associated elements, CSS states and Vite/Rollup plugins, plus practical tips on vertical slices and when to write or avoid bindings.
AI-written summary · about
chapters (16)
- 0:00Adopting Gleam incrementally
- 1:57Cultural and technical concerns
- 3:01Gleam’s syntax and types
- 5:09Slow incremental adoption
- 6:33Gleam libraries in Elixir
- 7:40Gleam compiles to Erlang/JS
- 9:11Removing Gleam safely
- 9:34Calling Elixir from Gleam
- 10:41Cleaner Gleam bindings
- 11:47FFI boundaries
- 12:32Transition to JavaScript
- 13:16Gleam’s JS tooling
- 14:22Web components in Gleam
- 15:48Gleam in Phoenix
- 16:10Production readiness
- 16:52Question and answer session








