comment on

I think you're looking it partly from the wrong angle. Some of the Perl books were published 2 or 3 years ago, but those that haven't been updated for the most part don't need it.

I have C books that are around 20 years old and are still current for learning the language. Just because a book is old doesn't mean it isn't worthwhile.

However, I do agree that Java (and VB) take up far too much space on the shelves. I also agree that the use of CGI in the book title has started to be seen as a bad thing. Too many CGI application written in Perl have had bad press simply because of bad experiences from several years ago. Perl has been getting a facelift in recent times and some of the really good books (such as Perl & XML, Perl for Bioinformatics and even Perl for System Administration) will hopefully make people more aware that there is more to Perl than CGI.

But how do we change this? One way is to write lots of reviews for the Perl books you have and add them to various sites to give them a bit more notoriety.

Also if you are asking for a particular book and $bookstore doesn't have it in stock, ask them to do a look up to see how much it is and when it would be available. Some stores record look ups to see what people are requesting. If a book is getting more requests, but it's always out of stock, very quickly you are likely to find in back on the shelves.

At the end of the day, it's all about promotion.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Barbie
Birmingham Perl Mongers
Web Site: http://birmingham.pm.org/
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

In reply to Re: Re: Re: The Black Art of Perl Programming? by barbie
in thread The Black Art of Perl Programming? by Anonymous Monk

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


good chemistry is complicated, and a little bit messy -LW
	PerlMonks