A developer who primarily uses Rust for personal projects published a blog post detailing their experience trying Gleam, a functional programming language that compiles to the Erlang VM (BEAM) and can also target JavaScript for use with Node.js. The post highlights Gleam's simple syntax, its interoperability with Erlang and Elixir, and draws comparisons to Rust, noting that much of the code they wrote in Gleam could reportedly be adapted to Rust with minimal changes.
nchagnet.eu
· 2026-11-09
Gleam version 1.19.0 introduces a new Erlang code generator that outputs Erlang abstract forms instead of source code. This change enhances build performance, improves metadata accuracy for debugging, and raises code quality standards within the compiler. The update reflects a significant shift in how Gleam integrates with the Erlang ecosystem, focusing on efficiency and precision.
gleam.run
· 2026-10-06
A developer detailed a new static-site publishing setup for the Byzantine Systems blog that keeps writing entirely inside Emacs using Org-mode, while replacing an earlier Nix-and-scripts pipeline with a smaller, typed toolchain. The stack combines Org-mode and Babel for authoring, d2 for diagrams, Pandoc for conversion, Nix/flakes/devenv to pin the environment, and Gleam with Blogatto and Lustre to generate HTML without a separate templating language.
byzantine-systems.github.io
· 2026-10-02
The authors have retracted their paper on warming and global drought severity after discovering multiple errors, including failure to use area-weighted grid cells, inadvertent use of an outdated dataset (GLEAM v3 instead of GLEAM4), and a timestepping bug that misclassified data periods. They also acknowledged unclear explanations of how an arid-region mask was applied across different figures. Rather than issue a correction, the authors chose to retract the paper entirely and plan to resubmit a fully revised version for new peer review.
nature.com
· 2026-09-02
A developer frustrated by inconsistent Erlang and JavaScript outputs from the Gleam compiler first tried using an LLM to generate edge-case test programs, spending about $20 in tokens to surface just one confirmed bug (issue #5613), which was promptly fixed. Dissatisfied with the cost and randomness of that approach, they pivoted to building a structure-aware fuzzer that generates syntactically valid Gleam programs automatically to systematically probe the compiler for hidden defects.
kurz.net
· 2026-08-25