If your program gets into a funky state, it's much simpler to trash it and start over, than to try to work backwards to a safe state. Sysadmins know this at the

If your program gets into a funky state, it's much simpler to trash it and start over, than to try to work backwards to a safe state. Sysadmins know this at the os-process and machine level, Erlang brings it to the language level. Erlang was designed for robustness, concurrency was just a happy side-effect of that focus.