Mo

Home

❯

directions

❯

Direction 8: BEAM qualities without the BEAM

Direction 8: BEAM qualities without the BEAM

Properties1
tagsruntime

Sep 17, 20261 min read

Direction 8: BEAM qualities without the BEAM

Compile to a single static binary, memory-efficient like Rust or Go. A small runtime linked into the binary (like Go’s scheduler) is acceptable; a separate VM is not. (Reframed by d36-vm-first-runtime: the bytecode VM is the reference runtime and the C backend an ahead-of-time compilation of it; the binary is still one static file.)

Related

  • d36-vm-first-runtime
  • d24-compile-to-c-via-zig
  • steal-list
  • d25-interpreter-for-the-edit-loop

Graph View

  • Direction 8: BEAM qualities without the BEAM
  • Related

Backlinks

  • The eight camps of language design
  • PL history: 1980s through 2000s
  • PL history: 2010 through September 2026
  • Mo synthesis: what history says to Mo
  • Research agenda, Sep 2026: Fable's response to the contradictions
  • Steal list: what to take from other languages
  • Direction 24: Compilation target: C via the Zig toolchain for release, own fast backend for the edit loop
  • Mo
  • The thesis and its evidence
  • Hermes research monitoring
  • Mo vs Elixir
  • Mo vs Unison
  • Author: Joe Armstrong (Erlang)
  • Language landscape: which languages deserve a deep comparison
  • Reliability and testing philosophies
  • Erlang / BEAM — Let It Crash, Then Restart
  • Research agenda, Sep 2026: recent papers, language authors, and the manifestos beyond Tiger Style

Created with Quartz v5.0.0 © 2026

  • GitHub
  • Discord Community