24 Mar 2013, 03:29
Generic-user-small

Tamara Temple (2 posts)

I loved this book, not so much for the metaprogramming “spells” as for the absolutely lovely unpacking of Ruby’s Object Model. I wrote a review over at “Goodreads.com”http://www.goodreads.com/review/show/569268658 and gave it 5 stars.

There are a number of errors in this edition (Kindle version) where there are missing words and phrases. It was a bit annoying, so I hope these get fixed in future editions. There is the ever-present problem of reading a technical book on the Kindle as well where some of the code snippets extend off the page.

25 Apr 2013, 08:45
Photo_17_pragsmall

Paolo Perrotta (42 posts)

Thank you, Tamara! Reviews like yours are my energy source now that I’m working on the second edition of the book.

If the Kindle problems are still there in the latest download of the book, can you report one or two of them on the errata page? (http://pragprog.com/titles/ppmetr/errata) Our Kindle process is still kinda new, and apparently it still has a few wrinkles.

25 Apr 2013, 18:45
Photo_17_pragsmall

Paolo Perrotta (42 posts)

(BTW, if you don’t have the time to go to the errata page, I’d really appreciate one or two examples of the problem, even right here in this forum).

15 Oct 2013, 03:37
Generic-user-small

Jeff Parrish (1 post)

I concur that your book did a brilliant job of explaining the Ruby object model. The best I’ve seen to date. In spite of that, I came across what might be an “edge case” that I can’t understand. Basically, it involves a comparison of class inheritance and module inclusion. They almost behave the same.

If you are interested, what is the preferred way to provide you with a very small example that illustrates the issue? (The answer might be useful for your 2nd edition)

  You must be logged in to comment