11 ms·

This is on my Christmas list to my fam. I've been looking forward to reading it ever since ErlangCamp, which was organized by some of the authors, and fully a

by chops 16y ago

This is on my Christmas list to my fam. I've been looking forward to reading it ever since ErlangCamp, which was organized by some of the authors, and fully awesome. If the book's as helpful as ErlangCamp was, then I expect this book to deepen my understanding of OTP, which in the O'Reilly and PragProg books seem to be more of a "if you want, you can do OTP". I prefer the "this is the way it should be done" approach. OTP should be the norm, rather than the exception, and a lot of new Erlang developers miss that (including myself).

martinjlogan 16y ago
You are right on target. OTP should be the norm and should be learned as a first step. Later on for curiosities sake one can learn to program without it! OTP codifies many of the best practices that experts in this type of process based concurrency model use every day. It is nice to be finished with the book and we are really proud of it. These days we are back to Erlware, resurrecting the project from a two year hibernation, and also planning for the next ErlangCamp.
- gordonguthrie 16y ago
  Martin, one of the problems with Joe Armstrong's book and OTP is that Joe doesn't use OTP - he always rolls his own servers - bless him. I remember everyone giving him dogs abuse for it over dinner at the Erlang Users Conference 3 or 4 years ago. I do think we need to be all GNU/Linuxy about it and just always refer to it as Erlang/OTP.
silentbicycle 16y ago
The other books spend more time easing the reader into concepts like immutability, pattern matching, supervision hierarchies, and the concurrency model. This book is for when you're sold on Erlang-the-language's overall design, but still not sure about how to set up a real project on Erlang-the-platform. I'd recommend getting all three, or one of the other two and this one. I like the Armstrong book's personality more - Cesarini's seems better organized, but a bit too serious. Also: ErlangCamp was indeed fully awesome.

by chops 16y ago

martinjlogan 16y ago

You are right on target. OTP should be the norm and should be learned as a first step. Later on for curiosities sake one can learn to program without it! OTP codifies many of the best practices that experts in this type of process based concurrency model use every day. It is nice to be finished with the book and we are really proud of it. These days we are back to Erlware, resurrecting the project from a two year hibernation, and also planning for the next ErlangCamp.

gordonguthrie 16y ago
Martin, one of the problems with Joe Armstrong's book and OTP is that Joe doesn't use OTP - he always rolls his own servers - bless him. I remember everyone giving him dogs abuse for it over dinner at the Erlang Users Conference 3 or 4 years ago. I do think we need to be all GNU/Linuxy about it and just always refer to it as Erlang/OTP.

silentbicycle 16y ago

The other books spend more time easing the reader into concepts like immutability, pattern matching, supervision hierarchies, and the concurrency model. This book is for when you're sold on Erlang-the-language's overall design, but still not sure about how to set up a real project on Erlang-the-platform. I'd recommend getting all three, or one of the other two and this one. I like the Armstrong book's personality more - Cesarini's seems better organized, but a bit too serious. Also: ErlangCamp was indeed fully awesome.