This Post Has 12 Comments

1. Short but shock full of great inspiring chapters on how to build cool and useful things using Erlang
   Brilliant book. The book demonstrates clearly how Erlang works and how it’s a simple language with simple primitives to handle things that other languages struggle with.After an introduction to how to do things sequentially we’re then ushered into how the primitives for concurrency work and what they enable, but also what they mean in terms of error handling and how you will need to structure your networks of processes in order to make your system robust.When we’re comfortable with the concurrency primitives and how to handle them comes a part about how to interface with external resources and how this is typically (ideally) done in Erlang. A SHOUTcast server is demonstrated before moving on how to interface with websockets; a very powerful chapter demonstrating the simplicity of how Erlang can communicate with an external process.When we’re done with the multitude of ways you can use websockets we jump straight into data handling; ETS- and DETS-tables. This flows into a chapter about the Mnesia database.After a chapter about debugging and tracing (which is quite unique in Erlang) we are introduced to OTP, the Open Telecom Platform (“The name is actually misleading, because OTP is far more general tan you might think”, indeed). After a good introduction to how the generic server module is structured and created (introducing callbacks and how they work) we’re then introduced to how to make a system using OTP.At this point, one might be inclined to put the book down and that would be fine, but to close the book out there are several chapters on useful idioms, what to aim for in terms of how to interface with external processes, using external dependencies and perhaps most importantly what to think about when you’re trying to use multiple cores effectively.

   Reply

2. Best style of teaching and erlang
   I am impressed by this book for its style of teaching and its content about erlang. It is one of the best technical books I have read in my life.Style-wise, this book is easy to read. Takes you from knowing nothing about erlang to very advanced techniques. And does this in a very clear, concise way with just enough source code and problems. I really liked the way author teaches the topic.Content wise, this book is about erlang and it has everything one needs in easy to gtab chunks. It might be slightly expensive compared to other books but totally worth it, especially you are learning it from the horse’s mouth, hahaha.I feel like I have everything I need to write erlang code with just this book.

   Reply

3. Some like the prose style of the Learn You Some Erlang …
   Everyone has a different learning style. Some like the prose style of the Learn You Some Erlang book. While that book was also interesting and educational, it didn’t fit my learning style nor serve as well a future reference as this book by Joe Armstrong. I tend to evaluate software books by the following three criteria: content (does it provide good examples?, e.g. for use as a cookbook for programming tasks), how it expands my mind (does it trigger new questions and new ways of thinking?), and lastly whether it is organized well for future reference (e.g. well indexed and organized into conceptual chapters). Some books excel at one or two of these areas (e.g. Learn You Some Erlang mostly excels at the first two), but Joe’s book excels at all three. Plus some of the examples that the Learn You Some Erlang provided weren’t as clear to me in terms of understanding them as Joe’s. Sorry to compare two books against each other – they’re currently the only two Erlang books I’ve read to now.

   Reply

4. A must have.
   masterfully written and all the examples are clearly defined. This book a cut above the rest for newbies like myself wishing to learn the language. The book cleanly and easily explains what takes books like “Learn you some erlang for great good.” or “Introduction to Erlang programming” a while, or just can’t explain. It cleanly takes you from the beginning and provides examples that will get you thinking in erlang from the start. A must have for any serious Erlang programmer. It easily explains how to start and process and WHY we start processes to do work. Other books spend pages and pages boring you to death on an example that isn’t well chosen, or just fail to describe what Elang is. The author, one of the Erlang creators describes everything so clearly that I wish I didn’t sound so over the top, but go ahead read some of the free same amazon provides. You’ll see im not over the top.Buy it. You won’t regret it.

   Reply

5. mindblowing read
   As a newcomer to the Erlang, this is an absolutely essential book to anyone getting familiar with this amazing functional, concurrent language. The creator of Erlang masterfully explains the language through excellent real world examples and great analogies to imperative language constructs familiar to experienced programmers and newcomers. I love the creator’s thinking process expressed throughout the book. It really helps you realize the possibilities of using Erlang capabilities to solve problems in a intuitive manner that is not possible with imperative languages. This last comment may sound ridiculous, but reading the book was so enlightening and mindbending that I forgot where I was like Alice in wonderland did.

   Reply

6. Excellent Book – This New Copy Arrived in Used/Dirty Condition
   Do get this book. Joe Armstrong is a rare treasure for his contribution to our craft and industry and to all humans for the things in the world from which we all benefit – like telephone and internet switches that have so robustly run Erlang.Not sure why the copy that arrived at my home at the new price was dirty and smeared with ink stains.The content of the book is absolutely 5 stars – the quality of this print copy was 2 stars.

   Reply

7. Interesting Language to Learn
   Overall, the book is very well written. Erlang has many forward thinking ideas being focused around concurrency, having an optional type system, an in memory nosql database, etc. It’s a language that is interesting to learn even if it does not end up being your bread and butter winning tool.

   Reply

8. Un des meilleurs livre de programmation que j’ai pu lire.Joe Armstrong distille des conseils et des techniques tout au long du livre consacré à son langage.On y comprends mieux Erlang et sa force. Ne vous laissez pas avoir par la syntaxe.

   Reply

9. If you want to get into Erlang, this is the book for you. Joe Armstrong is one of the creators of Erlang (many people call him “the” creator of Erlang), and the book is infused with his thinking, not a dry guide to the language.Part 1 – Why Erlang? This introduces the concept of concurrency, and explains that modern computers have multiple cores. But writing programs which can take advantage of multiple cores is hard, far harder than it should be. Indeed, there’s a view that this is acting as a huge constraint on how the likes of Intel take processor chips forward. Erlang was designed to run across multiple processors, and so fits the modern multicore world like a glove.Part 2 – Sequential Programming. Here he gets into the nuts and bolts of “ordinary” Erlang programming i.e. integers, lists, strings, functions, etc. He also introduces pattern matching, which is a powerful way of getting the right bit of code called, relieving the programmer of much boilerplate coding. This section is needed in all programming books, not much more to say about it.Part 3 – Concurrent and Distributed Programs. This is where the fun starts. He explains all about Erlang processes, which are NOT operating system processes, but mini processes simulated by the Erlang VM. They’re kind of “green threads”, and they are so lightweight that there can be millions of them in one server. Then they can be distributed over many servers, with a bit of effort but not with so much effort that it kills you.The Erlang way of handling errors is covered next. Imagine having millions of processes running at the same time, and all the interactions that can occur. What happens when you have a bug, or some weird environmental thing happens, and one of your processes dies? In a Java multi-threaded application, the app would die; so much work is done trying to stop that from happening. In Erlang, you just let the process die, and the system fires up a new one. Everything was designed in from scratch to handle large-scale software, processes, and sets of servers.Part 4 – Programming Libraries and Frameworks. Here we’re told about interfacing Erlang with other languages, using sockets, websockets, the inbuilt database support, and tools like profilers and debuggers. Then we get a description of OTP, a huge and battle-tested library ready for us to use. We also get told here about hot code swapping – the ability to replace live code while the system continues to run: this allows you to build a system which can run for years at a time, without the need to bring it down for maintenance. No wonder the WhatsApp people chose Erlang.Part 5 – Building Applications tidies up any loose ends, including Erlang programming idioms.All in all, an excellent book. You don’t need to be an Erlang expert to read it. Or even know any Erlang at all before you start. You’ll end up being proficient at Erlang, with the foundation to be able to turn yourself into an expert. What is fascinating is learning how a master developer thinks.

   Reply

10. The book is organized and structured in a way for a novice to learn and understand the concepts of Erlang in a very short time. The content is laid out concisely. Very satisfied.

    Reply

11. While Erlang is indispensable when it comes to make your computer-model isomorphic to real-world, learning and understanding Erlang with Joe is a serious fun. I have been programming Erlang for quite a few years now, but Joe’s book (1st edition until now, and now this 2nd edition) is still finding its time & place to be present in opened state on my desk. The same passage keeps on illumining its deeper and deeper meaning and application to real-world situations over time – and then, you know, why Joe has chosen to write that passage, and how much distance you have come through since you read it for the first time. While there are other useful and worthy books on Erlang, you realise Joe is different. What K&R did to C in that classic book, Joe does it to Erlang in this one. Seriousness is not compromised anywhere even for the decades-long experienced programmers, but this book doesn’t compromise on fun either.

    Reply

12. Joe Armstrong ist eine ziemlich interessante Persönlichkeit (einfach auf Youtube mal die Interviews anschauen) die zweite Auflage versucht recht gut, Grundlagen zu Erlang zu vermitteln. Diese Sprache ist so gigantisch und umfassend wie keine andere und man kann das Buch sehr gut lesen. Für Distributed Computing und “gewisse” damit zusammenhängende “Spezialgebiete”, OTP und Mnesia sollte man sich aber zusätzliche, separate Bücher zulegen, weil jedes Thema für sich schon jeweils locker 500 Seiten und mehr benötigt – selbst dann ist man noch bei den Grundlagen. Wer einmal Erlang lernt, der wird eindeutig davon angezogen. Das ist kein Gerücht – sondern eine Tatsache. Für die Web-Entwickler: Erlang ist nicht wie PHP, es gibt separate Web-Frameworks aber auch DAS ist wieder ein Thema für sich allein. Erlang ist eine Art in sich geschlossenes System, das gestartet wird. Programme werden darin “eingeladen” und ausgeführt. Man kann TCP-Server erstellen oder Prozesse miteinander Daten austauschen lassen. Der Rest steht im Buch *g

    Reply