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.
  • Do you think there's any connection to the fact that you had a very open development process, with a repository, a mailing list, and open participation by the community in shaping the book?

    I'm not saying there is, necessarily, but I know that I definitely had a better impression of what I'd get out of the book based on what (little) I put into it and what I saw others putting into it. Certainly, this was one book that seemed to come about quite differently than most others in that sense.

    Or it may be that a true advanced Perl book was a niche that was begging to be filled E.g. I thought Advanced Perl Programming, 2nd ed., was anything but. Mastering Perl had content that I really don't have repetitively in many other things on my shelf.

    -- dagolden
    • I have no way to really tell. I'd have to run a control test, and I don't want to spend two years doing that :)

      I definitely think the quality of the book is related to opening it up. There's a very long list of acknowlegements, and it was very handy to have a test audience for things like negative lookaround (my hardest topic to write about). Now, if the better quality means more sales I don't know. It could be that I just talked about it every chance I get so it gets more attention that other books. Who kn