1. 19
  1.  

  2. 6

    This is a great read.

    One of the things I’ve seen that’s missing with Erlang is more practical documentation like this.

    For instance, all the books yammer on about ‘let it crash!’ but almost none of them mention the concept of a ‘circuit breaker’ like fuse ( https://github.com/jlouis/fuse ) which is vital if you have, say, a web site and you don’t want it to just ‘crash’ if the DB is down for a bit.

    1. 5

      The author of this book wrote Learn You Some Erlang, which is fairly practical though focuses on teaching OTP concepts.

      There’s probably going to be more “practical” documentation for Elixir.

      1. 3

        Yes, I’m well aware of who he is. He’s a great guy and super helpful.

        The point being is that there are a lot of ‘concepts’ docs in the Erlang world, but I found that there is a need for “going beyond the concepts to the real world” documentation.

    2. 1

      I think this book needs a glossary. Or at least a footnote that defines “OTP” as “Open Telecom Platform” when used in an Erlang-specific context.

      I’m not sure that a Three Letter Acronym (TLA), such as “OTP,” should be presumed to be common knowledge.

      Aren’t books supposed to provide complete information about abbreviations, whenever possible?

      1. 5

        This is a book aimed very specifically at intermediate/advanced Erlang users.