Skip to content
0:00 / 0:00

#gleam#beam#statictyping

Louis Pilfold on Building Gleam - Static Types on the BEAM

BEAM There, Done That

921 subscribers • 17 videos on Hallway

YouTube
  • Recommended by 1 person: 1 in engineering communities.
  • Presented by Louis Pilfold, creator of Gleam

Intermediate. Assumes working knowledge.

1.6K views1 month ago1 recommendation

Programming languagesSystems programmingLanguage design and type systemsCompilers and interpretersElixir and Erlang

Louis Pilfold explains the design decisions, challenges, and regrets behind building Gleam, a statically typed language for the BEAM.

What if the BEAM had a language that felt like talking to a friend instead of fighting a compiler? That's the problem Louis Pilfold set out to solve. He loved the BEAM. He missed static types. Every other option was a tradeoff he couldn't live with. So he built Gleam - and after years of quietly saying no to everything he wasn't sure about, it's gathered a community, found production users, and now runs on servers, browsers, and $2 microcontrollers. Topics include: why every successful language is born from a problem - and what specific frustration made Louis start building rather than just complaining the discipline of saying no: no if, no currying, no pretending two targets are one world the design decision Louis regrets most - the conditional compilation syntax he's now stuck with and desperately doesn't want more people to use why Gleam's concurrency model lives in a library rather than the language - and what that buys in terms of flexibility when smarter people eventually improve it how Gleam solved the problem everyone said was unsolvable: "you can't type message passing on the BEAM" what the JavaScript and BEAM targets share and where they genuinely can't be unified - and why pretending they can leads to terrible architecture why Gleam chose Erlang records as its data structure and what that costs at runtime Lustre, Gleam's web framework - beating mainstream JavaScript frameworks in benchmarks while written entirely in Gleam how Louis funds his work on Gleam: GitHub Sponsors, the Gleam community, and what sustainable open source actually looks like from the inside what Gleam will look like in 3–5 years - native records, better JavaScript interop, and why the language's approach to stability makes those changes possible Recorded August 20, 2026. Resources mentioned: gleam.run - docs, tour, community tour.gleam.run - interactive language tour running the Gleam compiler compiled to Wasm, takes an afternoon Exercism Gleam track Code Crafters - build Redis/SQLite/Git in Gleam GitHub Sponsors: lpil (Louis Pilfold) Lustre - Gleam's web framework

Why it's here

1 person recommends this

What people say. Recommended for its discussion on Gleam's design, its JavaScript target, and the creator's regrets regarding conditional compilation.

u/ancatrusca0in r/elixir • Recommends

…Also notable: Lustre, Gleam's web framework that compiles to JavaScript, already outperforms mainstream JavaScript frameworks in benchmarks. The JavaScript target isn't a second-class citizen. He also covers the one language feature he regrets shipping - the conditional compilation syntax - and why he's quietly hoping nobody else discovers it. [video…