Ahh, I'm actually thinking of a book like that for a typical 10-page web-based application, using CGI::Prototype, Template::Toolkit, and Class::DBI. Well, not exactly thinking of it... more like being encouraged strongly by my clients to write such a book to give a broader overview than all the details that are out there so far.

The problem with books is that unless your book is wildly successful, you end up getting paid roughly minimum wage to write it. And no, I'm not kidding. I could make more money flinging hamburgers than writing some of the books I've written. {grin}

So, the purpose of writing a book is to act as a credential, or to be done as a labor of love, or to support a class as a textbook. I already spend time here (and everywhere else) as a labor of love, so I'm sort of labored out there. And I really don't need another credential.

The third option is intriguing, but I'm not sure what the classroom sales would be of a course that covers the "small web app" market. The problem isn't that there aren't a lot of people doing it: there are! The problem is getting 10 to 20 of them in the same room for a week. Ugh.