I’ve gone through the first 50 pages of your book and it’s been great! Keep up the good work
Lance, thank you for your book. It is amazing, I am really enjoying it! Will there be something related on how to persist data? Thank you!
Thanks @ryanswapp! So glad you’re enjoying the book!
Wow, I really enjoyed what I’ve gone through so far! Was pleased to see a game as an example project, being a game developer myself it boosted my interest a lot Thanks for your work!
Thanks for the kind words @kpanic. Glad you like the book!
I know we won’t cover storing and retrieving application state the way we might with a standard MVC web app. Since the book isn’t in its final form yet, I’m not sure whether we might touch on some form of persistence somewhere. Until it’s done, it’s not done.
@lance, if you do decide to do a chapter on persistence can you use Mnesia or CouchDB?
This book sounds fantastic. I’m gonna convince my boss to order me one
Thanks! Glad you’re enjoying the book, @artvin.
@jeramyRR, I think it’s really unlikely that we would cover any specific technology for persistence.
I would personally stick to Phoenix defaults (Postgres) as I imagine that’s what most will be using.
Also, re updating to Phoenix 1.3, I would definitely recommend doing so, particularly if there’s not much in it - people love books that cover the latest most up-to-date versions (one of the reasons so many of us love Pragprog, they seem to continually update their books)
I woke up early this morning and got a chance to read a few chapters already before work and after getting home.
Loving the book already lance.
A great perspective, technically and otherwise, (including the flower child version of a wwII era game).
I knew asking for CouchDB was a long shot, but Mnesia seems doable right?
Thanks @Cortrah! So glad you appreciate the book and the game!
This is an instant purchase because the first chapter is called “Build a Game Engine in Pure Elixir”. I love books that start with non-trivial projects instead of “let’s build a todo list”.
Just purely from a sales perspective, I’d strongly advise you to update it to 1.3. People are going to look at the book, see that Phoenix 1.3 is out and then see the book covers 1.2…and that will make them hesitate. You’re going to have a much longer sales cycle for this one if it gets updated for 1.3.
@lance sure, I understand Maybe you could put some hints in a paragraph covering storage possibilities.
Anyhow, keep up the good work! thanks again!
+1 for expanding into persistence.
I couldn’t agree more!
Nice book, already started the journey, its cool that you just start diving in into the business logic, but I really miss Tests. After the first Module (Coordinates) it would be better to just start with tests. It would actually save much more time, because you don’t need to go to the console and test it manually.
This book does not teach Phoenix, however. You probably should have some knowledge of it when starting reading it.