> Now that's a loaded title, and I know some people will > immediately see it as a personal slam on Erlang or > ammunition for berating the language in various

> Now that's a loaded title, and I know some people will > immediately see it as a personal slam on Erlang or > ammunition for berating the language in various forums. Instead, this is actually a quite good discriminator for those that understand high availability programming in Erlang and those that do not. E.g. Erlang is about programming in the presence of failure, not about having eliminated everything that could possibly fail.