Firstly, I have only started reading your book (in an eclectic manner) and I find it very useful. I own both the printed and the Kindle edition. The printed edition would probably just grace my bookshelf if… well if it wasn’t for…
The Kindle edition has a few really severe drawbacks.
First, it is totally useless in the reference section (ironically), because it lacks certain indexing and browsing facilities. Kindle search just doesn’t cut it. And it is not realistic to page through hundreds or possibly thousands of locations page-by-page.
What I would like to see is:
- Each major section (as now found in the TOC) has a landing page with links to subsections.
- Each subsection has another landing page with sub-subsections (we might be at class level here).
- Each class has a landing page with links to its methods etc.
- An actual keyword index might be useful.
Another nuissance are the graphic illustrations which have been downsized and compressed to death. Really, they have no practical use whatsoever. Even if you enlarge them and look at the enlargements with a magnifying glass, you can’t read the printed text, because the resolution is so poor and then on top of that there are jpeg artifacts.
I would very much appreciate if this could be improved in a future edition.
Also, I got curious about extending Ruby with the C language (actually, possibly using Ruby and RSpec to behaviour-drive C language modules when reading the RDoc section. Unfortunately, the subject of how to write C extensions seems to be outside of the scope of the book.