Gleam Was Created by Louis Pilfold and First Released in 2016

Gleam started life in 2016 as the personal project of British developer Louis Pilfold, who wanted a friendly language for the Erlang virtual machine. It was first released on 13 June 2016, which means the language you can install today is nearly a decade old even though it talks and feels brand new. When a language has a gestation that long, the sensible reaction is not skepticism. It is respect for careful, deliberate design.

Why does the origin date matter to you as an engineer? Because it explains the shape of the tool you reach for. Pilfold did not set out to build the thousandth language that compiles to JavaScript. He set out to fix a real pain he had hit while working with Erlang and Elixir on the BEAM, the battle tested virtual machine that powers telephone switches and distributed systems. The BEAM is astonishingly good at fault tolerance and concurrency. What it was missing, from his point of view, was a statically typed language that was pleasant to read.

Erlang has types, of course, but they are optional and are effectively documentation with no guarantees. Elixir made the BEAM approachable but stayed dynamically typed. Gleam was Pilfold's attempt to keep everything developers love about the BEAM, its actors, its supervision trees, its ability to recover from crashes, while adding a compiler that can prove your types before anything runs.

The 2016 release date also matters because it shows how honestly the project grew up. The very first versions of the compiler were written in Erlang itself. That prototype worked, but as the language got bigger Pilfold found the lack of static types in his own implementation made refactoring painfully slow. So he rewrote the compiler in Rust, a decision documented in the project's frequently asked questions and one that directly explains the tool's speed today. A compiler that had to be salvaged through a rewrite still shipped a stable 1.0 in the end.

There is a practical lesson here that applies to any senior developer evaluating new tooling. A long running solo project is not a sign of stagnation. It usually means the author had a specific problem and was willing to iterate until the solution was right. When you adopt a language like Gleam, you are betting on that kind of patience in the maintainership, and the 2016 start date is evidence you can point to.

You can verify the release date yourself in seconds. The official organization on GitHub lists tags going back to 2016, while the site at gleam.run documents the full version history. If you are weighing Gleam for a new service, take ten minutes to read that history. It will tell you more about the philosophy of the project than any benchmark ever could.