After The Crash

on YouTube ↗44m

" summary

Explains what “let it crash” means in Erlang and what happens afterward, focusing on letting processes crash and the resulting effects on software design. Discusses Erlang’s approach to distributed-systems programming and how its process-failure model influences application architecture.

AI-written summary · about

" related talks

• 43mLearning to Live with ErrorsTomas Petricek · GOTO Chicago 2018
• 49mKeynote: How to sell Elixir (Again)Evadne Wu · Code BEAM Lite Stockholm 2023
• 40mComparison and Commentary on "Application Operating System"C. Thomas Stover · Erlang Factory SF Bay Area 2014
• 15mTowards Verifying Crash ConsistencyKeonho Lee, Conan Truong, Brian Demsky · OOPSLA 2025
• 37mModern Abstractions and the Web, and avoiding Pitfalls because Life is shortIrina Guberman · Code Mesh 2015
• 43mThursday Keynote -- What Programming is Really AboutMike Williams · Erlang Factory SF Bay Area 2014
• 29mFractured Processes: Adaptive, Fine-Grained Process AbstractionsAndrea C. Arpaci-Dusseau, Remzi H. Arpaci-Dusseau, Thanumalayan Sankaranarayana Pillai · TRIOS ’14
• 47mThe Tension Between Expediency and CorrectnessJosh Adams · NDC London 2017