> First, because you still need to implement all these supervisors yourself anyway so the complexity is still there. Have you implemented an erlang/elixir supe

> First, because you still need to implement all these supervisors yourself anyway so the complexity is still there. Have you implemented an erlang/elixir supervisor? It's not hard. It would probably take me about 60 seconds. > Besides, Erlang doesn't have the monopoly on "let it crash": plenty of languages have better ways to catch and recover from errors, either through exceptions or algebraic data types that allow the compiler to make sure you have covered all the error cases. Simply handling the error is not the primary reason for "let it crash". The reason for let it crash is to have the remainder of the system continue to make forward progress and with minimal disruption. I think if anything the greatest thing about let it crash is that I can have a relatively green junior put something into prod without worrying that an uncaught error will bring down the whole system.