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'm currently reading it now. I guess I can whip up a review and post it somewhere.

    I went straight to chapter 8 after the first chapter or two (whatever was recommended). I like to have an example to look through to understand the basics and then I can dive into the depths of the API as needed.

    Would it have been better to move chapter 8 up and have that be what the reader is exposed to first? I guess I'll have to finish reading it and make my thoughts known.
  • 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 fea
  • Bug everyone you know to post a Amazon review. And reassure people that an Amazon review doesn't have be a grand exegesis like a Slashdot review -- it can just be a few sentences.

    And BTW, yes, maybe convince someone to write a Slashdot review. Michel's Slashdot review of my book seemed to definitely get people's attention.

  • Shameless self-promotion is good. I did talk to some people at the Mpls PM meeting last night who liked the book, and I asked them right up a review on Amazon. Maybe I should send something to the Mason users list too.

    I think Andy (last name?) (petdance) is planning to write a review for The Perl Review, and that's a good thing. If anyone reading this wants to write a review for Slashdot, I'm sure ORA will send you a copy of the book (hell, _I'll_ send you one!).
  • Just for the other people out there, who don't have a paper copy of the book: the entire book is available online as HTML, at its site: TOC [masonbook.com]

    So far, I've only read chapter 1, comparing Mason to the other template Perl modules out there, and to PHP, and I must say: I like it. It gives me enough incentive to, one day, try out mod_perl+Mason. Without it, the threshold would just be too high.

    And, of course, one day I'll read (most of) the rest of the book. Maybe even buy it. But I'll have to be hooked on Mason