It seems to me that there are too many book reviews for a simple list. I think it is time some kind of categorization was introduced.

As a simple fix, maybe just enlarging the font of the title, or italicizing the 1-liner, would help make a visual scan of the page easier.

Replies are listed 'Best First'.
Re: Book Reviews getting unmanageable
by davido (Cardinal) on Sep 24, 2003 at 17:42 UTC
    I agree, and would also add that it would be helpful if part of the header for each review included edition number.

    We're now on Camel III, Learning Perl III, CGI Programming with Perl II, soon to see (rumor has it) Mastering Regular Expressions II, not long until we see a Perl Cookbook II, etc. While Camel has been good from the get go, I don't think anyone would argue with the assertion that the first edition of the mouse book (CGI Programming on the WWW) was far inferior to the second edition of the mouse book (CGI Programming with Perl). Ok, bad example because the title did change a little even though it's still the mouse book. But still it would be nice if one could quickly surmise whether or not a particular review was written for the 3rd edition or the 5th edition.

    Just a thought...

    Update: Corrected a wording to clarify my meaning.

    Dave

    "If I had my life to do over again, I'd be a plumber." -- Albert Einstein

      Adding the edition info would be good, but it is meaningless without saying how many editions exist (is it the first edition of one, or the third edition of six?), which would require some system of updating as new editions are released. Someone would have to be constantly checking to stay current. As a for instance, the 2nd edition of The Perl Cookbook was released in August, 2003, and the 2nd of Mastering Regular Expressions in July. Simply noting that both reviews were of first editions wouldn't reveal that.

      Having said that, I still think adding edition info is important. And, I would love to see the author(s) of the book as well as the author of the review. With the redundancy in title names, it's pretty hard to distinguish one from another sometimes. Something like "Title, Edition, Author(s), Year of publication, and Publisher" would go a long way towards uniquely identifying the object under discussion. Of course, just including the ISBN would do that, too, but it isn't very "human readable".

      At the same time, "Mastering Algorithms with Perl by splinky" might be a great review (in fact, I think it is), but someone who knows neither splinky nor the fact that the book in question is:

      "Mastering Algorithms with Perl by Jon Orwant, Jarkko Hietaniemi & John Macdonald ISBN 1-56592-398-7 Copyright 1999, O'Reilly & Associates, Inc."

      could be forgiven for passing it up just from ignorance (that is, lack of information).

      I love books and I love the book reviews. Even in their present state, I think they are one of the most valuable resources in the monastary. Anything that would improve their usablility would be a "Good Thing."

      <tangent>
      I don't think anyone would argue that the first edition of the mouse book (CGI Programming on the WWW) was far inferior to the second edition of the mouse book (CGI Programming with Perl).

      Actually, if, as I suspect, you mean argue with the claim that rather than "argue that", then I would.

      A lot happened between 1996 and 2000. In 1996, the Mouse was the best book in its class. I'm not so confident that was true in 2000, by which time the competition had grown considerably.

      The first edition's language-agnostic approach was not only appropriate for the time period (i.e. before Perl got the "duct tape of the internet" reputation) it provided a better overview of the real topic: CGI.

      In contrast, the second edition took a kitchen-sink approach with whole chapters on subjects like email and data persistence. And then, when it came to discussing CGI itself, the second edition might as well have been renamed CGI.pm Programming with Perl as, after the first 25% of the book or so, just about every example was based on CGI.pm.

      In short, the first edition was a good focused book about CGI and the second was YAPB (yes, that's "Yet Another Perl Book") with the wrong color cover.

      In the interest of full disclosure...

      I'm probably biased because I learned CGI from the first and nothing from the second. I purchased the second edition simply because I was struggling with a severe, debilitating addiction to purchasing O'Reilly books and it was that week's fix. Had I taken the time to carefully inspect the book while still standing safely in the aisles of Border's rather than just giving into my obsession with those shiny green, pink, and blue covers, I might have realized it contained almost nothing that wasn't better presented in the Camel, the Rhino, the Pelican or the first edition Mouse, all of which I already owned. But no. I bought it and dealt with my disappointment by telling myself that the extra inch on my second shelf of critter books was well worth it.

      I'm much better now. I've been clean, sober, and O'Reilly free for almost 2 years. Ok... Ok... but I have been O'Reilly free. Well, mostly. I do still pull a few old favorites off the shelf now and again, though. :-)

      </tangent>
      -sauoq
      "My two cents aren't worth a dime.";
      
        Lol. Ok, well, I wasn't expecting an argument, but at least we agree that the two editions were different enough that any review of the first is less than applicable to the second.

        As for why I feel the first edition of "Mouse" was inferior:

        • It doesn't discuss CGI.pm, despite the already strongly asserted existance of that module. Instead, it discusses only CGI::Lite and cgilib.pl.
        • It is very lightweight with respect to discussion of security, despite security already being a significant issue in 1996.
        • It shows step by step how to create a webmail gateway, but doesn't really discuss the fact that a wide open webmail gateway is a spam-house's dream.

        I consider those pretty big oversights for a book on CGI, even in 1996.

        Dave

        "If I had my life to do over again, I'd be a plumber." -- Albert Einstein

Re: Book Reviews getting unmanageable
by LazerRed (Pilgrim) on Sep 24, 2003 at 20:07 UTC
    First, davido++ to the good suggestion, but I think it is up to the poster to specify in the title, to be accurate that is.

    I was thinking, if the reviews go through the normal approval process, couldn't part of it be a catagory designation/assignment? Have catagory headings on the page such as Programming General, Programming Perl, Programming Other, Computers General, Computers Security, etc... Maybe it would help to break-up the page a bit? Just a thought.

    LR

    Whip me, Beat me, Make me use Y-ModemG.