BEAM There, Done That

← BEAM There, Done That5 dagen geleden · 1 u 12 min

Louis Pilfold on Building Gleam - Static Types on the BEAM

Louis Pilfold on Building Gleam - Static Types on the BEAM5 dagen geleden1 u 12 min

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