@lance, how’s the beta update going? I have to say I deeply admire the way you’ve handled feedback from the forum. I can’t wait to dive in to your next release!
jeramyRR
alathon
@lance: Just a thought → It might be really interesting to save the old version of the game at that point in the book (the one you’re currently rewriting to be different), to be able to compare it with the new one. For me, many good insights come from looking at ‘This is one way we could do X, here are the pros/cons’, and ‘This is the idiomatic (IMO) way to approach doing X, it has these pros/cons’. I don’t know whether that fits into the structure of the book, but if not directly in there, then maybe as an errata / some way to be able to compare the code of both approaches at the same point?
6
lance
Author of Functional Web Development with Elixir, OTP, and Phoenix
jeramyRR
kokolegorille
untra
I’ve been following the examples in the book, and for the most part implementing the code in my own github repo. I just implemented the redone chapter 2 (with tests as well!)
I originally did the first three chapters before it was announced chapter 2 would be redone. When chapters 3 and 4 are redone, I intend to implement those as well.
I have learned a lot about OTP and good elixir development from this book so far. Having done the chapter 2 exercises before and after beta, I want to say the updated exercises better reflect the business logic of the application.
1
kokolegorille
lance
Author of Functional Web Development with Elixir, OTP, and Phoenix
Thanks @jaimeiniesta! Glad you’re enjoying the book. 
We will cover data persistence for disaster recovery, but we haven’t quite gotten there yet. Stay tuned. 
I would also add that you can hold a surprising number of processes in memory on the BEAM. At work we routinely and comfortably run 800,000 processes on a single node.
3