Keynote: We are stronger together

on YouTube ↗57m

" summary

Claims the BEAM ecosystem has over 30 languages and suffers fragmentation while the VM remains the stable core, argues for a monorepo for the BEAM with automated CI that continuously pulls OTP changes (WhatsApp-style scripts already catch regressions), proposes a curated packaging/store, asks for standard interoperability like ETF supporting protobuf/json and a single build/deploy format, and suggests compiler-hooks and shared type/checker infrastructure so compile‑time features (macros, types) interoperate across languages.

AI-written summary · about

" chapters (11)

1. 0:0003:53 - Intro
2. 3:5406:37 - The Ecosystem
3. 6:3808:40 - The Business Part
4. 8:4110:54 - Multi-dimensional Challenge
5. 10:5511:49 - The Onion Theory
6. 11:5020:06 - Erlang and Elixir
7. 20:0722:41 - GLEAM, LFE and more
8. 22:4232:54 - Monorepo for the BEAM
9. 32:5538:02 - Interoperability
10. 38:0347:25 - F.O.M.O
11. 47:2756:51 - Compilation and Types

" related talks

• 54mKeynote: AdoptionBrian Cardarella · The Big Elixir 2019
• 43mClosing KeynoteBoydMulterer · ElixirConf 2016
• 48mGetting to Know the Erlang Virtual Machine, the BEAMNorberto Ortigoza · Mexico City Erlang Factory Lite 2015
• 19mErlang/OTP UpdateBjörn Gustavsson · Code BEAM Lite Stockholm 2026
• 52mKeynote: Pilgrim's Progress to the Promised LandRobert Virding · Elixir LDN 2016
• 38mMembrane Framework: Bringing BEAM into multimediaMarcin Lewandowski · Code BEAM SF 2019
• 43mThe RiverBruce Tate · Code Elixir LDN 2019
• 47mPurescript on the BEAM; Typed OTP for greatnessRob Ashton · Code Mesh LDN 2019