Q&A Panel Discussion
summary
Panelists debate concrete tradeoffs: cryptographic work uses NIFs or external Rust/OpenSSL bindings because pure Erlang/Elixir is CPU‑slow; binary pattern matching has documented performance tips; Dialyzer-style static checks run too slowly for per‑save use; real systems are event‑driven APIs, push/notification pipelines and IoT backends using Nerves with per‑device heartbeats; telemetry moved from Elixir to Erlang for broader reuse; the ecosystem sorely needs supervisor trees ergonomics and faster tooling plus Phoenix LiveView for high‑throughput UI updates.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 0:48Cryptography in Erlang/Elixir
- 4:54Fixing one thing in BEAM
- 13:05BEAM strengths
- 14:12Supervisor trees for Java devs
- 17:40BEAM vs JVM actors
- 19:52Code versioning in Erlang
- 23:50BEAM app types
- 27:55BEAM in IoT
- 31:10Erlang on devices
- 32:20Immutable data in Elixir
- 36:28Erlang vs Elixir
- 40:59Erlang succinctness vs Elixir
- 44:04Phoenix in web dev
- 47:40Closing remarks
related talks
48mQ&A Panel Discussion With Code Beam Lite India Speakers
01h 05mQ&A with Chris McCord & José Valim
27mLive Q&A Session – Anca Agape
01h 01mLightning Talks - Part II
47mPanel Discussion - Theia and the Cloud Development Ecosystem Where it fits now and what do
52mFireside chat on client libraries
29mLive Q&A Session – Liane Praza
14mLive Q&A 4 with Speakers