If it was published, that page would be updated
MJDs blog is still active
| [reply] |
"Computer Books" per se seem to be a lot less frequent these days, except maybe on Kindles, because they are (with a few rare exceptions) money-losing propositions. There are other cheaper, more profitable ways to establish yourself as an authority. | [reply] |
And on kindles, the typography tends to be abysmal.
"@" for a or "&"; type sizes of examples unreadably-tiny (i.e., far worse than this) and effectively unchangeable; even missing pages (esp. errata).
Some of these problems occur with mainstream fiction, biography, etc., but it seems that whatever the process for conversion, it's badly flawed and perhaps, un-mastered by tech publishers.
Afterthought: did you subscribe to the "low volume" announcement list at the page you listed? (Links, here, BTW, need only a URL enclosed by square brackets; links with text which is different than the actual content take a pipe between URL and copy-to-be-rendered.)
| [reply] |
I agree. Most normal books are fine, plus/minus the odd OCR problem for older books. Computer books are much harder to OCR, because spellchecking doesn't work. The only thing that can parse Perl is perl...
I think my biggest disappointment for me was the Kindle version of Perl Best Practices. Perl::Critic depends heavily on page numbers which the Kindle version doesn't support. Otherwise this would be a very good, portable reference (the printed PBP is quite heavy, and mine is starting to loose pages because of constant going back-and-forth through the pages).
If Damian is reading this: I would pay good money for a PerlModule version of the book i can just plugin to P::C that shows me the POD version of the full text for any guideline that just popped up in testing.
Sorry for any bad spelling, broken formatting and missing code examples. I broke my left hand and i'm doing the best i can here...
| [reply] |