What do you think?
Rate this book
Developing Games With Ruby
At day you have to wrangle with legacy code, fix bugs, struggle with APIs, deploy services and integrate things. Yet you wish you could create worlds, animate dragons, break laws of physics and design artificial intelligence. You can.
Read the full book online: https://leanpub.com/developing-games-...
Read the full book online: https://leanpub.com/developing-games-...
253 pages, ebook
First published October 27, 2014
1 person is currently reading
3 people want to read
Ratings & Reviews
Friends & Following
Create a free account to discover what your friends think of this book!
Community Reviews
Displaying 1 of 1 review
October 22, 2019
About 2/5 through the book, the author stops recording all of the changes he makes to the source code. It is impossible to directly follow along with the book and try to code the game by hand because only about half of the changes are actually recorded and explained.
For example, I followed along with the book up to chapter 4. Chapter 5 is supposed to refactor the code, so I followed along making all the changes that the author did. After trying to run the refactored application, I ran the game and was presented with errors. After addressing error after error I looked at the example code on his GitHub and realized that some of the code in his GitHib for this chapter is not present in the book... Okay, fine, in this case the missing code was not that significant; you can figure out what to needs to be changed if you have a feel for the codebase and you aren't an absolute programming beginner. However, then I moved on to implementing the changes in chapter 6 which is supposed to add physics. Again, half the changes that are made from chapter 5 to chapter 6 in his GitHub are not recorded. And this time some of the code that IS shown in the book is not even correct!! It does not match up with the code he has written on GitHub and when it runs it gives the wrong results!
Because of this, the book feels incomplete, as if the author completely forgot to do quality control. If you're reading it just to scan through the book and get an overall feel of how to make a game like this, maybe its okay. If you're trying to follow along like I would image 90% of people would want to do, avoid this book and find a different one that is actually complete.
For example, I followed along with the book up to chapter 4. Chapter 5 is supposed to refactor the code, so I followed along making all the changes that the author did. After trying to run the refactored application, I ran the game and was presented with errors. After addressing error after error I looked at the example code on his GitHub and realized that some of the code in his GitHib for this chapter is not present in the book... Okay, fine, in this case the missing code was not that significant; you can figure out what to needs to be changed if you have a feel for the codebase and you aren't an absolute programming beginner. However, then I moved on to implementing the changes in chapter 6 which is supposed to add physics. Again, half the changes that are made from chapter 5 to chapter 6 in his GitHub are not recorded. And this time some of the code that IS shown in the book is not even correct!! It does not match up with the code he has written on GitHub and when it runs it gives the wrong results!
Because of this, the book feels incomplete, as if the author completely forgot to do quality control. If you're reading it just to scan through the book and get an overall feel of how to make a game like this, maybe its okay. If you're trying to follow along like I would image 90% of people would want to do, avoid this book and find a different one that is actually complete.
Displaying 1 of 1 review