Optimising for maintainability - Gleam in production at Strand

Since go-live, the Gleam code within Strand’s application has been rock-solid. “We’ve had zero Gleam-related crashes, and even when there have been issues with other parts of the system, the BEAM has kept everything running,” says Ed Kelly. “We’ve been able to fix problems without our users even noticing that anything was wrong.”

Amazing to hear success stories of Gleam in production, running on the beam really feels like a super power

How is debugger support for Gleam these days?

Last time I checked, I think it was “use the target platform debugger”, where you end up debugging the js or elrang output code.

While I generally don’t mind “printf style debugging”, I have had to work with many codebases in the past where being able to use a debugger was a godsend.