[phtrivier]

> "Let it crash" means bringing a supervisor with simple behavior (usually restart) or human into the loop when you leave the happy path.

If a "human" has to enter the loop when a crash occurs, this limits the kind of system you can write.

I had to work on a system where a gen server was responding to requests from a machine, sent frequently (not high frequency, but a few times per second.) If for some reason the client misbehaves, or behaves properly but happens to use a code path that has a type error, the only option given by "let it crash" was to, well... crash the actor, restart the actor, then receive the same message again, crash the actor, restart the actor, etc... and eventually you crash the supervisor, which restarts and receives the same message, etc...