<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Perl Cookbook, Second Edition</title>
	<atom:link href="http://www.cgiphp.com/blog/perl-cookbook-second-edition/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.cgiphp.com/blog/perl-cookbook-second-edition/</link>
	<description>Enhance your site with CGi, PHP and ASP scripts</description>
	<lastBuildDate>Sat, 04 Feb 2012 18:32:35 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: Anonymous</title>
		<link>http://www.cgiphp.com/blog/perl-cookbook-second-edition/comment-page-1/#comment-164</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Sat, 06 Feb 2010 15:06:43 +0000</pubDate>
		<guid isPermaLink="false">http://bloghost.xaviermedia.net/blog/perl-cookbook-second-edition/#comment-164</guid>
		<description>There are so many errors in the book (about 350 errors). It was said that the book was hurried to meet the deadline (for Perl Conference). I suggest to wait until they fix them in the second edition.
Rating: 1 / 5</description>
		<content:encoded><![CDATA[<p>There are so many errors in the book (about 350 errors). It was said that the book was hurried to meet the deadline (for Perl Conference). I suggest to wait until they fix them in the second edition.<br />
Rating: 1 / 5</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: S. Krishnaswami</title>
		<link>http://www.cgiphp.com/blog/perl-cookbook-second-edition/comment-page-1/#comment-163</link>
		<dc:creator>S. Krishnaswami</dc:creator>
		<pubDate>Sat, 06 Feb 2010 13:26:40 +0000</pubDate>
		<guid isPermaLink="false">http://bloghost.xaviermedia.net/blog/perl-cookbook-second-edition/#comment-163</guid>
		<description>for a beginner like me this book was a second read after I finished the llama book.. bit bulky but worth the money
Rating: 3 / 5</description>
		<content:encoded><![CDATA[<p>for a beginner like me this book was a second read after I finished the llama book.. bit bulky but worth the money<br />
Rating: 3 / 5</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Luis D. Patino</title>
		<link>http://www.cgiphp.com/blog/perl-cookbook-second-edition/comment-page-1/#comment-162</link>
		<dc:creator>Luis D. Patino</dc:creator>
		<pubDate>Sat, 06 Feb 2010 12:57:10 +0000</pubDate>
		<guid isPermaLink="false">http://bloghost.xaviermedia.net/blog/perl-cookbook-second-edition/#comment-162</guid>
		<description>The book, excelent.. but I had problems with the delivery. Fortunally I bougth it to Amazon and they sended to me another book. When I have used UPS or FEDEX I have not had any problem, but with the normal mail, please I don&#039;t want it anymore..
Rating: 5 / 5</description>
		<content:encoded><![CDATA[<p>The book, excelent.. but I had problems with the delivery. Fortunally I bougth it to Amazon and they sended to me another book. When I have used UPS or FEDEX I have not had any problem, but with the normal mail, please I don&#039;t want it anymore..<br />
Rating: 5 / 5</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymous</title>
		<link>http://www.cgiphp.com/blog/perl-cookbook-second-edition/comment-page-1/#comment-161</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Sat, 06 Feb 2010 11:22:51 +0000</pubDate>
		<guid isPermaLink="false">http://bloghost.xaviermedia.net/blog/perl-cookbook-second-edition/#comment-161</guid>
		<description>Don&#039;t spend money on this book. Unless you are a beginner with no experience you will not learn anything new from it. Programming Perl is a much better book that contains all of the information found in this book plus x10 more.
Rating: 2 / 5</description>
		<content:encoded><![CDATA[<p>Don&#039;t spend money on this book. Unless you are a beginner with no experience you will not learn anything new from it. Programming Perl is a much better book that contains all of the information found in this book plus x10 more.<br />
Rating: 2 / 5</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jo Totland</title>
		<link>http://www.cgiphp.com/blog/perl-cookbook-second-edition/comment-page-1/#comment-160</link>
		<dc:creator>Jo Totland</dc:creator>
		<pubDate>Sat, 06 Feb 2010 09:03:53 +0000</pubDate>
		<guid isPermaLink="false">http://bloghost.xaviermedia.net/blog/perl-cookbook-second-edition/#comment-160</guid>
		<description>When I first looked at this book, it seemed like a good idea. Perl is sufficiently arcane for there to be lot&#039;s of simple solutions that will not be immediately obvious. However, the book has two major faults. It is too thick, and it is too specific.&lt;p&gt;What I had hoped for was something like &quot;Design Patterns&quot;, but for Perl. But instead of trying to generalize, this book tries to list every specific problem that the beginning Perl programmer is likely to meet. For that reason it is unreadable. Any real insight is bound to get hidden in between dozens of trivial tasks. And when you actually meet some problem you think would be a good idea to look up, it is unlikely to be exactly the same as the authors envisioned (why not simply write a library instead?).&lt;p&gt;With the general incompetence level in the IT-sector during the dot-com bubble, it is possible this book needed to exist, but today it seems like a monument of stupidity, a useless reference that will catch dust forever.
Rating: 1 / 5</description>
		<content:encoded><![CDATA[<p>When I first looked at this book, it seemed like a good idea. Perl is sufficiently arcane for there to be lot&#039;s of simple solutions that will not be immediately obvious. However, the book has two major faults. It is too thick, and it is too specific.
<p>What I had hoped for was something like &#034;Design Patterns&#034;, but for Perl. But instead of trying to generalize, this book tries to list every specific problem that the beginning Perl programmer is likely to meet. For that reason it is unreadable. Any real insight is bound to get hidden in between dozens of trivial tasks. And when you actually meet some problem you think would be a good idea to look up, it is unlikely to be exactly the same as the authors envisioned (why not simply write a library instead?).</p>
<p>With the general incompetence level in the IT-sector during the dot-com bubble, it is possible this book needed to exist, but today it seems like a monument of stupidity, a useless reference that will catch dust forever.<br />
Rating: 1 / 5</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.277 seconds -->

