Gleam’s Core Team Panel at the Inaugural Gleam Gathering 2026

Published on YouTube – 11 hours ago – 8 minutes 37 seconds
Panelists: Louis Pilfold, Giacomo Cavalieri, Hayleigh Thompson, Surya Rose; moderated by Isaac Harris‑Holt

---

Thesis

The opening session of Gleam Gathering 2026 served not merely as a promotional showcase but as a candid audit of Gleam’s journey from a niche functional language to a growing platform for reliable, concurrent systems. By tracing the framework’s origins, assessing its present state, and projecting a concrete roadmap, the core team underscored a philosophy that balances strict type safety with pragmatic tooling, a stance that may shape the future of functional programming on the JVM, BEAM, and WebAssembly ecosystems.

---

Key Arguments

1. The why behind Gleam’s inception

Louis Pilfold reminded the audience that Gleam was born out of frustration with the brittleness of JavaScript‑centric stacks when building distributed services. The team sought a language that could guarantee no runtime type errors while still compiling to multiple runtimes (Erlang/OTP, JavaScript, native). Their early design decisions—explicit algebraic data types, exhaustive pattern matching, and a pure functional core—were deliberately chosen to eliminate entire classes of bugs that surface only in production.

2. Progress on the compiler and ecosystem

Giacomo Cavalieri highlighted recent advances in the Gleam compiler:

• Incremental compilation now reduces rebuild times by up to 40 % for large codebases, a direct response to community feedback about developer ergonomics.
• Improved interop with existing Erlang libraries, thanks to a new NIF‑friendly ABI that allows seamless calls to native code without sacrificing safety.
• WebAssembly target reached production‑grade stability, enabling Gleam to run in browsers and edge environments with deterministic memory usage.

These technical milestones demonstrate that Gleam is no longer a curiosity project; it is a viable alternative for services that demand high reliability.

3. Community‑driven tooling and documentation

Hayleigh Thompson emphasized the role of the community in shaping Gleam’s tooling. The gleam‑format tool, now integrated into popular editors (VS Code, Emacs, Vim), enforces a canonical code style, reducing diffs in pull requests and making code reviews smoother. Moreover, the newly launched Gleam Book (available at https://gleam.run/book) consolidates tutorials, best‑practice guides, and migration paths from other functional languages, lowering the barrier for newcomers.

4. Governance and sustainability

Surya Rose addressed the governance model, noting the transition from a founder‑centric decision process to a community‑elected steering committee. This shift aims to distribute responsibility for roadmap prioritization, security audits, and release cadence, ensuring that Gleam’s evolution reflects a broader set of stakeholder needs. The panel also announced a sponsor program that funds part‑time contributors, a move intended to improve long‑term sustainability without compromising the project’s open‑source ethos.

---

Implications for Developers and the Broader Ecosystem

1. Reliability at scale – Organizations that already rely on Erlang/OTP for fault‑tolerant systems can now adopt Gleam to write new services with stronger compile‑time guarantees, reducing the operational overhead of runtime crashes.
2. Cross‑runtime portability – The ability to compile the same Gleam codebase to both BEAM and WebAssembly opens new architectural patterns, such as sharing business logic between server‑side services and client‑side edge functions.
3. Talent acquisition – As functional programming gains traction in industry (e.g., Rust, Elixir), Gleam offers a gentle learning curve for developers familiar with pattern matching and immutable data, potentially widening the pool of engineers comfortable with highly concurrent code.
4. Toolchain convergence – The emphasis on editor integration and formatting standards may push other language communities to adopt similar practices, fostering a more uniform developer experience across disparate ecosystems.

---

Counter‑Perspectives

While the panel painted an optimistic picture, some critics argue that Gleam’s runtime performance still lags behind hand‑optimized Rust or Go in CPU‑bound workloads, primarily due to the overhead of the BEAM VM when targeting native platforms. Additionally, the small size of the ecosystem—fewer third‑party libraries compared to more mature languages—means that early adopters often need to write their own adapters, which can offset the safety benefits. The panel acknowledged these concerns, noting ongoing work on a standard library expansion and performance benchmarks that target specific use‑cases such as high‑throughput message processing.

---

Conclusion

The core team panel at Gleam Gathering 2026 succeeded in delivering a balanced narrative: Gleam has matured from an experimental language into a production‑ready platform, yet it remains honest about the challenges that lie ahead. By investing in compiler performance, community governance, and cross‑runtime capabilities, Gleam positions itself as a compelling option for developers who value correctness and concurrency. Whether the language will achieve mainstream adoption will depend on continued ecosystem growth and the community’s ability to translate its technical merits into tangible business value.

---

For a full recording of the panel, see the YouTube video.