3 ms·
This is great. I can attack the few chapters I skipped over in Joe's most recent book[1] that required R17. [1]: http://pragprog.com/book/jaerlang2/programming
by NDizzle 13y ago
This is great. I can attack the few chapters I skipped over in Joe's most recent book[1] that required R17.
[1]: http://pragprog.com/book/jaerlang2/programming-erlang http://pragprog.com/book/jaerlang2/programming-erlang
- fidotron 13y agoI have to say, this is one of my favourite programming books, even though I've never been paid to write any Erlang at all. Just the insights into how to go about building reliable systems are inspiring and profoundly affected my work in other languages. That and it's written in a brilliantly approachable style.
- NDizzle 13y agoYes, it's really good. Don't worry. I can't write any erlang either. I'm still in the try-hard phase.
- Shish2k 13y ago> Just the insights into how to go about building reliable systems are inspiring I found that too; I wonder if the programming community would be better off if more people were pushed towards Erlang? Similar to how every programmer should know C, so that when they write python they have some idea what's happening under the hood, it would be good for every programmer to know Erlang/OTP so they learn how large-scale reliable systems should work?
- rdtsc 13y agoI agree. It is just useful to have the ideas and paradigms used in one's toolbox. Concurrent isolated units working together by sending messages. That is interesting and can be implemented in other systems. Like say using a message broker like RabbitMQ or 0mq and isolated processes. Or the idea of supervision. Have a supervisors OS process watch and restart its workers and so on. Those can be implemented and applied without even touching Erlang itself.
- Buttons840 13y agoThank you for mentioning this book. I intend to learn Erlang after I finish studying Haskell, and I'll probably use this book because of your recommendation.