Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • I thought that it made sense to have it _after_ the chapters that cover the various things used in the chapter. Of course, the chapters before that cover lots of other things which aren't used in the site as well, so maybe it would still work to have chapter 8 earlier (like maybe after chapter 3).

    But in the end, there's nothing that _forces_ people to read straight through from start to finish. I for one don't actually like reading big example apps and I prefer the parts that are just explanations of features. But that's just me.

    One possibility for a future edition would be to build up the example site from scratch throughout the book. The problem with this is that I think that tends to lead to a more artificial example, because you need one that can be built up bit by bit. But with a real app, there's often a threshold of required knowledge needed before you can reasonably start.

    Anyway, I figure one bad review is nothing to get too upset about. We've gotten good feedback from other readers. I'm just hoping that people will post good reviews on Amazon so that potential buyers don't get turned off by seeing one review that's bad.