Armstrong's book is the single best source for documentation about Erlang I have found so far. I consider it a must read for anyone who is going to be looking i

Armstrong's book is the single best source for documentation about Erlang I have found so far. I consider it a must read for anyone who is going to be looking into using Erlang. I had a beta copy of it about two months before it was published and it helped me tremendously by simplifying some of the design patterns I had constructed myself. Also, if I had to complain about Erlang at all the documentation is the one thing I would complain about. I find so many useful features by reading the source code (which also makes my own code better by reading other peoples code) that are not documented that I often wonder who is choosing what to document and what not to. For instance, the to_lower() function to make a string lower case is in the http_util module, instead of the string module. Took me six months to find it and I had written my own in the mean time, theirs is much more efficient, but all but undocumented.