There is a sense in which it is not possible to write a similar book for other languages. Erlang's "Let it crash" design philosophy is more or less unique among languages used as much as more than Erlang. This means the definition of 'trouble' which requires troubleshooting will tend to be different when trouble is not an error in business logic. Likewise the details of implementing solutions will be different, for example handling a high frequency of crashes by making 10x the number of concurrent actors available to the system.

{A Love Song to Erlang} I think Erlang is a beautiful piece of engineering design as engineering design. I would not say that about any other language and find other languages beautifully designed for other reasons. But Erlang is an engineer's tool designed based on engineering principles. The abstractions are engineering abstractions...but with garbage collection.