If curious see also<p>2018 <a href="https://news.ycombinator.com/item?id=17003897" rel="nofollow">https://news.ycombinator.com/item?id=17003897</a><p>2017 <a href="https://news.ycombinator.com/item?id=14061985" rel="nofollow">https://news.ycombinator.com/item?id=14061985</a>
Back in my day, BEAM was also this <a href="https://en.m.wikipedia.org/wiki/BEAM_robotics" rel="nofollow">https://en.m.wikipedia.org/wiki/BEAM_robotics</a>
PDFs of the beam book available here: <a href="https://github.com/happi/theBeamBook/releases" rel="nofollow">https://github.com/happi/theBeamBook/releases</a>
A bit off-topic: Is there an overview of OTP's design and usage patterns that assumes the reader has minimal Erlang knowledge? I have no Erlang experience, but I am interested in what makes OTP so revered.
please put Erlang somewhere in the title, theres so many titles I click because the title isn't descriptive enough and I don't want to miss out in case it happens to be a subject of interest.<p>I don't have a problem with Erlang, but it feels like unintentional clickbait if the title fails to convey what a reader may expect.