This very much falls into the category of rambling, non-essential observations - Perl-related, but certainly not Getting anyThing Done (TM). If you're not in the mood, you've been warned.

Last night I was browsing in a mega-Barnes&Noble and cursing their paltry selection of Perl books. Python had four or five shelves, Ruby as many or more, Ajax galore, PHP books in bundles, but two - count them - two books on Perl. So I'm annoyed, and I begin grumbling about languages-of-the-minute, and like that. I then notice that over against a nearby wall, there's quite a lot of books for C, C++ and Java. I wander over, and sure enough, that area has lots of Perl paper-based goodness.

Here's the punchline: the section with lots of Ajax, Ruby, Python and company was called 'Programming Languages', and the section with C, C++, Java, JavaScript (sic) and Perl books was called 'Professional Computing'.

After considering for a minute, I thought, "Good enough."

Replies are listed 'Best First'.
Re: The view from Barnes & Noble
by johndageek (Hermit) on Oct 09, 2008 at 19:35 UTC
    Take any combination of quality levels of any given thing (or widget if you prefer), bring these items into a large retail store/area, now select an employee at random and ask them to classify these widgets so they will fit in groupings we already have.

    Try this a couple of times, now try to find any one of the items.

    Just be glad you didn't have to look in the knitting and crafts area for perl books

    Enjoy!
    Dageek

      IMHO, the only reliable way to organise books on shelves is to sort by ISBN.

      Similarly, the only way to sort music is firstly by the first note played, and secondly by the quantity of drugs the composer was on at the time.

      Update:

      On reflection, I this comment was sub-consciously influenced by Borge's Animals. I think we could all benefit from a brief contemplation of this classification paradigm.

      --
      .sig : File not found.

        The only reliable way to organise books on shelves is to not organise them at all. If you sort by ISBN, then you're stuffed if you need to insert in the middle as you have to shuffle everything along, perhaps onto other shelves, which in turn means you have to move stuff on those shelves, and so on. The best way to organise books on shelves is to just put them wherever there's space, and use a searchable database to keep track of what's where.

        Anyway, sorting by ISBN is approximately the same as sorting by publisher. Which is what Foyles in London used to do. People hated it, and they only stayed in business because there were no other large bookshops nearby. Now that several others have opened, Foyles have adopted a much more sensible sorting algorithm - they mostly sort by subject, author and title. Although they do still have a seperate section for O'Reilly books.

      Each store/chain is free to do what they like, but most books now come from the publisher with a "default" section designation, typically printed on the upper left corner of the back cover.

      It isn't a cure-all, however, as some books have multiple suggestions — for example, Effective Java has:
      Java/Internet Programming/Programming Languages.

      Between the mind which plans and the hands which build, there must be a mediator... and this mediator must be the heart.
        I love it that in U.K public libraries they used to (and still do, in fact) organise their shelves by the Dewey Decimal system , which put subjects in this order:
        # 000 – Computer science, information, and general works # 100 – Philosophy and psychology # 200 – Religion # 300 – Social sciences # 400 – Languages # 500 – Science and Mathematics # 600 – Technology and applied science # 700 – Arts and recreation # 800 – Literature # 900 – History and geography and biography,
        and the 100's always seemed to attract the rather far out and wacky end of the spectrum.

        I always thought it entertaining that books on programming ended up sharing a shelf with Erich_von_Daniken ;-)

        This signature will be ready by Christmas
Re: The view from Barnes & Noble
by ikegami (Patriarch) on Oct 09, 2008 at 15:58 UTC
    What do you mean by the "(sic)"? You aren't even quoting.
      It was a (fairly lame) joke. I just meant that I found it odd to put JavaScript in the heavy duty section, as opposed to the web section or languages section. So the snarkiness of the sic was directed at that shelving choice rather than someone's words (as when you sic a quotation or something your editing).

      Frankly, I suspect JavaScript goes there for the simple reason that Java went there, and most people have no idea that they aren't the same thing.

        sic properly refers only to a misspelled or otherwise incorrect word, which you are leaving uncorrected for some reason (usually quotation). An ironic usage would be one where you want to imply that some word is misspelled or otherwise incorrect, even though it isn't. Doesn't make much sense beyond that.

        Anyway, ++ for the rest of your post.


        sas
      Sic is used to emphasize words, and is not limited to quoting (but doubtlessly quoting is where it's used most frequently).
        The page to which you link disagrees. "has been reproduced verbatim from the quoted original and is not a transcription error". And all the examples use quoted material.