# Programming Erlang (PragProg)

**URL:** <https://erlangforums.com/t/programming-erlang-pragprog/271>\
**Category:** Books\
**Tags:** book-programming-erlang, pragprog, erlang-books\
**Created:** [October 27, 2021, 2:23pm UTC](https://erlangforums.com/t/programming-erlang-pragprog/271 "2021-10-27T14:23:21Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![reymono](https://erlangforums.com/letter_avatar_proxy/v4/letter/r/e47c2d/32.png) [@reymono](https://erlangforums.com/u/reymono)\
**Post date:** [October 30, 2023, 1:18pm UTC](https://erlangforums.com/t/programming-erlang-pragprog/271/2 "2023-10-30T13:18:03Z")

</div>

Many of the Erlang books are getting a little long in the tooth considering the changes in the language and ecosystem - I have browsed several of them recently.

This one by Joe Armstrong is probably my favorite introduction.  
It is from 2013 (OTP17) and could do with a 3rd edition - of course Joe is unfortunately not around to do it.

The chapter on maps needs to be updated - syntax has changed and the examples don’t compile with the OTP26 release.

Book mentions several 3rd party tools - the list should probably be revised/updated.

Rebar is now Rebar3 - several tools come with Erlang; shell, debugger, mnesia etc. I think a tool like Rebar3 should be there too - a good build/package tool is really important. Newer languages always have them “included” - e.g. Nodejs, Rust, whereas older languages like C and Python don’t and have struggled to get a good default option…

---

_[View the full topic](https://erlangforums.com/t/programming-erlang-pragprog/271)._
