ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Languages & runtimes · #gleam
Learn how to implement fault-tolerant state management in Gleam using GenServers and Supervisors via the gleam_otp library to build resilient BEAM applications.
Gleam has no exceptions, so fallible code can turn into a staircase of case expressions. The `use` expression flattens it — here's how the sugar works, with a result.try pipeline and its trade-offs.
An architecture note on wrapping Erlang libraries from Gleam: private @external declarations, validating wrappers, tagged-tuple error contracts, and when to switch to OTP actors instead.
Learn how Gleam’s opaque types hide constructors, enforce compile‑time encapsulation, and let you evolve library internals without breaking user code.
Decide whether to compile Gleam to the Erlang BEAM VM or to JavaScript by weighing concurrency, fault tolerance, and deployment constraints. A side‑by‑side table, trade‑off analysis, and a concrete HTTP endpoint test guide help you pick the right target for your service.
Gleam says "Up to date" after you just edited a file, or the runtime crashes on a module you renamed. A diagnostic map from symptom to cause — mtime granularity, orphaned .beam files, dependency graph gaps, cross-target cache collisions, and CI cache poisoning — with the exact checks and fixes.
Learn how Gleam opaque types hide implementation details, improve encapsulation, and make refactoring safer, with a concrete counter example and notes on interop and limitations.
Learn how to define and use Gleam opaque types to encapsulate data, enforce API stability, and hide internal representation while providing a clean public interface.
Learn how to use Gleam OTP Supervisors to build fault-tolerant services using the 'let it crash' philosophy, process isolation, and restart strategies.
erlang