Keynote: How to sell Elixir (Again)
summary
Argues that Elixir/OTP lowers risk and code volume by turning many failure modes into manageable annoyances: a JRuby/Java migration using Erlang JInterface and digraph reduced error rate by 100x; LiveView supports nested UIs (three to four layers) and allowed dozens of live components; supervisors let processes restart instead of complex error checks (let it crash); implemented streaming zip generation to serve large archives without temp files; adoption now hinges on economic switching costs, hiring and library maintenance succession.
AI-written summary · about
chapters (22)
- 0:00Introduction
- 2:30Risk management
- 8:37Risk tolerance
- 18:45Hype cycle
- 19:25OTP
- 19:49Risk registry
- 20:10Risk registry examples
- 20:35Good fault tolerance
- 22:00Two databases
- 22:44Systemic questions
- 23:13Resilience
- 25:26Most important change
- 26:35Social proof
- 27:18Gambler
- 27:50Examples
- 33:43Sustainability
- 34:33Maintenance
- 36:00I am not your supplier
- 37:09Legacy of tomorrow
- 37:37Summary
- 40:17Conclusion
- 40:39Questions
related talks
41mKeynote Panel discussion: Erlang all the things
52mKeynote: Pilgrim's Progress to the Promised Land
01h 06mKeynote: What's Ahead for Elixir?
41mKeynote - Confident Elixir
03h 19mWorkshop - All Aboard The Elixir Express!
43mThe River
41mIdioms for building fault-tolerant applications with Elixir
01h 06mWhat every Node.js developer needs to know about Elixir