Gleam no longer generates Erlang source, outputs abstract forms; users desire native target support (Rust/Go)
Problem
Gleam has rewritten its code generator to output Erlang abstract forms instead of human-readable Erlang source. This change may affect users who need to inspect or modify the generated code, and has sparked community interest in supporting compilation to native targets such as Rust or Go.
Pain points
- Desire for Gleam to compile to native targets like Rust or Go for broader deployment
- Transition from readable Erlang source to abstract forms may impact workflows that need to inspect or modify generated code
Questions to verify
- Would you like Gleam to compile to native targets such as Rust or Go?
- Do you often need to inspect or modify the generated Erlang source code from Gleam?
- How does the abstract form output affect your workflow?
Evidence
quote · @anonymous
If it could compile (transpile) to a native target like rust or go, it would be truly perfect.
quote · @anonymous
Over the last few months Giacomo Cavalieri has entirely rewritten Gleam's Erlang code generator that has an entirely different design, and most notably, outputs a different format. Previously Gleam generated Erlang source code, now it generates Erlang abstract forms.
Disclaimer: this card is distilled by AI from community discussions as “pain point evidence”. It is a starting point for need analysis and validation, not a “validated market need”. AI has analytical limits; please open the original discussion above to manually verify before key decisions.