Erlang has what is called a "let it crash" philosophy. A VERY simplified explanation: The idea is that a code crash won't terminate the program, it will just restart that part of the code that crashed and try again.
This is my best guess to why the computer is on fire in this picture. Erlang code can be written to actually be able to run in that kind of environment. Code may crash and burn, but the program just continues to work anyway.