<?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: Making Modern Perl more visible</title>
	<atom:link href="http://techblog.geeksqueal.com/2010/02/10/making-modern-perl-more-visible/feed/" rel="self" type="application/rss+xml" />
	<link>http://techblog.geeksqueal.com/2010/02/10/making-modern-perl-more-visible/</link>
	<description>What is the use of repeating all that stuff, if you don&#039;t explain it as you go on?</description>
	<lastBuildDate>Thu, 02 Jun 2011 04:56:15 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Paulo</title>
		<link>http://techblog.geeksqueal.com/2010/02/10/making-modern-perl-more-visible/comment-page-1/#comment-9708</link>
		<dc:creator>Paulo</dc:creator>
		<pubDate>Thu, 02 Jun 2011 04:56:15 +0000</pubDate>
		<guid isPermaLink="false">http://techblog.geeksqueal.com/?p=83#comment-9708</guid>
		<description>I&#039;d have to agree to this: I think the Perl community is realizing that they need to change some things around. This is healthy regardless of the language. I don’t think it’s too late for Perl, it has such a following.

It&#039;s never too late.  Especially with the rapid changes in technology, systems, processes and the like...they need to continuously improve on things to stay in the business.  Just my two cents worth.

My Blog: &lt;a HREF=&quot;http://LuminesLaser.com.br&quot; rel=&quot;nofollow&quot;&gt;Drenagem Linfatica&lt;/A&gt;</description>
		<content:encoded><![CDATA[<p>I&#8217;d have to agree to this: I think the Perl community is realizing that they need to change some things around. This is healthy regardless of the language. I don’t think it’s too late for Perl, it has such a following.</p>
<p>It&#8217;s never too late.  Especially with the rapid changes in technology, systems, processes and the like&#8230;they need to continuously improve on things to stay in the business.  Just my two cents worth.</p>
<p>My Blog: <a HREF="http://LuminesLaser.com.br" rel="nofollow">Drenagem Linfatica</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bob</title>
		<link>http://techblog.geeksqueal.com/2010/02/10/making-modern-perl-more-visible/comment-page-1/#comment-42</link>
		<dc:creator>Bob</dc:creator>
		<pubDate>Wed, 10 Mar 2010 21:31:21 +0000</pubDate>
		<guid isPermaLink="false">http://techblog.geeksqueal.com/?p=83#comment-42</guid>
		<description>Interesting thought. I&#039;m not familiar with those items, but I tend to write pretty plain pages. I&#039;m trying to avoid changing everything from a &quot;web page&quot; into a &quot;JavaScript application.&quot; I&#039;m in the &quot;new != better&quot; camp, but I take your point that making sure Perl is present in the examples of the flashy/catchy/new stuff would be a help.

Looks like &lt;a href=&quot;http://www.trirand.com/blog/&quot; rel=&quot;nofollow&quot;&gt;jqGrid&lt;/a&gt; has a &lt;a href=&quot;http://www.trirand.com/jqgridwiki/doku.php&quot; rel=&quot;nofollow&quot;&gt;wiki&lt;/a&gt;, and they mention Perl, but I&#039;m not sure where the sample code might go, off the top of my head. Where do you think the best place to put a sample might be?

I jumped over to the &lt;a href=&quot;http://www.extjs.com/&quot; rel=&quot;nofollow&quot;&gt;Ext JS&lt;/a&gt; site, and while the &lt;a href=&quot;http://www.extjs.com/learn/Tutorial:Ext_StartUp_Guide#The_Demos_.2F_Examples&quot; rel=&quot;nofollow&quot;&gt;start-up guide&lt;/a&gt; only has a PHP example, the &lt;a href=&quot;http://www.extjs.com/learn/Tutorial:Basic_Login&quot; rel=&quot;nofollow&quot;&gt;basic login example&lt;/a&gt; in the &lt;a href=&quot;http://www.extjs.com/learn/Tutorials&quot; rel=&quot;nofollow&quot;&gt;&lt;i&gt;Tutorials&lt;/i&gt;&lt;/a&gt; section has a number of language-specific examples, including &lt;a href=&quot;http://www.extjs.com/learn/Tutorial:Basic_Login#Login.pl&quot; rel=&quot;nofollow&quot;&gt;one for Perl&lt;/a&gt;. I&#039;ve not seriously looked at it and can&#039;t vouch for its swellness, but it&#039;s there.

Other than the &lt;a href=&quot;http://www.extjs.com/&quot; rel=&quot;nofollow&quot;&gt;Ext JS&lt;/a&gt; and the &lt;a href=&quot;http://www.trirand.com/blog/&quot; rel=&quot;nofollow&quot;&gt;jQuery Grid Plugin&lt;/a&gt; items, what comes to mind as flashy/catchy/new, that doesn&#039;t have a Perl reference?

This sounds like a job for the &lt;a href=&quot;http://ironman.enlightenedperl.org/&quot; rel=&quot;nofollow&quot;&gt;Perl Ironman&lt;/a&gt; SWAT team. :) If 1/10 of the folks there dropped by and added just one example to their respective wikis, I bet it would blow their minds. :)</description>
		<content:encoded><![CDATA[<p>Interesting thought. I&#8217;m not familiar with those items, but I tend to write pretty plain pages. I&#8217;m trying to avoid changing everything from a &#8220;web page&#8221; into a &#8220;JavaScript application.&#8221; I&#8217;m in the &#8220;new != better&#8221; camp, but I take your point that making sure Perl is present in the examples of the flashy/catchy/new stuff would be a help.</p>
<p>Looks like <a href="http://www.trirand.com/blog/" rel="nofollow">jqGrid</a> has a <a href="http://www.trirand.com/jqgridwiki/doku.php" rel="nofollow">wiki</a>, and they mention Perl, but I&#8217;m not sure where the sample code might go, off the top of my head. Where do you think the best place to put a sample might be?</p>
<p>I jumped over to the <a href="http://www.extjs.com/" rel="nofollow">Ext JS</a> site, and while the <a href="http://www.extjs.com/learn/Tutorial:Ext_StartUp_Guide#The_Demos_.2F_Examples" rel="nofollow">start-up guide</a> only has a PHP example, the <a href="http://www.extjs.com/learn/Tutorial:Basic_Login" rel="nofollow">basic login example</a> in the <a href="http://www.extjs.com/learn/Tutorials" rel="nofollow"><i>Tutorials</i></a> section has a number of language-specific examples, including <a href="http://www.extjs.com/learn/Tutorial:Basic_Login#Login.pl" rel="nofollow">one for Perl</a>. I&#8217;ve not seriously looked at it and can&#8217;t vouch for its swellness, but it&#8217;s there.</p>
<p>Other than the <a href="http://www.extjs.com/" rel="nofollow">Ext JS</a> and the <a href="http://www.trirand.com/blog/" rel="nofollow">jQuery Grid Plugin</a> items, what comes to mind as flashy/catchy/new, that doesn&#8217;t have a Perl reference?</p>
<p>This sounds like a job for the <a href="http://ironman.enlightenedperl.org/" rel="nofollow">Perl Ironman</a> SWAT team. <img src='http://techblog.geeksqueal.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' />  If 1/10 of the folks there dropped by and added just one example to their respective wikis, I bet it would blow their minds. <img src='http://techblog.geeksqueal.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bob</title>
		<link>http://techblog.geeksqueal.com/2010/02/10/making-modern-perl-more-visible/comment-page-1/#comment-40</link>
		<dc:creator>Bob</dc:creator>
		<pubDate>Wed, 10 Mar 2010 21:10:13 +0000</pubDate>
		<guid isPermaLink="false">http://techblog.geeksqueal.com/?p=83#comment-40</guid>
		<description>Yeah, Perl has &quot;issues.&quot; Isn&#039;t that one of it&#039;s strengths, though? [Fight!] :)

I think it&#039;s a good thing there&#039;s more than one way to accomplish things. I would hope it would let folks figure out which was was &quot;best&quot; for some specific purpose. Sadly, there is a lot of &quot;cargo cult,&quot; cut-and-paste, this-is-the-way-of-our-forefathers, rote-learning code out there--in Perl and every other language.

One of the things I liked about the Perl Cookbook was the emphasis on &lt;i&gt;why&lt;/i&gt; something worked the way it did. Yes, it let me get &lt;i&gt;this thing&lt;/i&gt; done &lt;i&gt;right now&lt;/i&gt; but it also gave me the reasoning behind the sample so I could get a better grasp on when (and when not) to do something.

I think a lot of Perl coding advice should come with a freshness date. I&#039;m starting to think my (only half-kidding) suggestion about changing the name of the language is a better and better idea. It would certainly help folks find avoid &quot;help&quot; that was only relevant for ten- to fifteen-year-old Perl versions.</description>
		<content:encoded><![CDATA[<p>Yeah, Perl has &#8220;issues.&#8221; Isn&#8217;t that one of it&#8217;s strengths, though? [Fight!] <img src='http://techblog.geeksqueal.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>I think it&#8217;s a good thing there&#8217;s more than one way to accomplish things. I would hope it would let folks figure out which was was &#8220;best&#8221; for some specific purpose. Sadly, there is a lot of &#8220;cargo cult,&#8221; cut-and-paste, this-is-the-way-of-our-forefathers, rote-learning code out there&#8211;in Perl and every other language.</p>
<p>One of the things I liked about the Perl Cookbook was the emphasis on <i>why</i> something worked the way it did. Yes, it let me get <i>this thing</i> done <i>right now</i> but it also gave me the reasoning behind the sample so I could get a better grasp on when (and when not) to do something.</p>
<p>I think a lot of Perl coding advice should come with a freshness date. I&#8217;m starting to think my (only half-kidding) suggestion about changing the name of the language is a better and better idea. It would certainly help folks find avoid &#8220;help&#8221; that was only relevant for ten- to fifteen-year-old Perl versions.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: lupin</title>
		<link>http://techblog.geeksqueal.com/2010/02/10/making-modern-perl-more-visible/comment-page-1/#comment-5</link>
		<dc:creator>lupin</dc:creator>
		<pubDate>Thu, 11 Feb 2010 05:42:44 +0000</pubDate>
		<guid isPermaLink="false">http://techblog.geeksqueal.com/?p=83#comment-5</guid>
		<description>One thing to help promote use of Perl, is to put forward working examples on things that matter/catchy to new web dev people. Say for example the jqgrid/extjs..etc almost all example/working codes you can see are Php/Ruby/Python, where&#039;s Perl?

 It is hard for newbie to find example codes, let alone docs that are working on this trendy/hype tools with Perl as server side language.</description>
		<content:encoded><![CDATA[<p>One thing to help promote use of Perl, is to put forward working examples on things that matter/catchy to new web dev people. Say for example the jqgrid/extjs..etc almost all example/working codes you can see are Php/Ruby/Python, where&#8217;s Perl?</p>
<p> It is hard for newbie to find example codes, let alone docs that are working on this trendy/hype tools with Perl as server side language.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Frank Gutierrez</title>
		<link>http://techblog.geeksqueal.com/2010/02/10/making-modern-perl-more-visible/comment-page-1/#comment-3</link>
		<dc:creator>Frank Gutierrez</dc:creator>
		<pubDate>Wed, 10 Feb 2010 19:18:10 +0000</pubDate>
		<guid isPermaLink="false">http://techblog.geeksqueal.com/?p=83#comment-3</guid>
		<description>I&#039;m also a Perl dev.  I&#039;m love Perl but hate some of its issues.  A common Perl saying, &#039;There&#039;s more than one way to do it&#039; seems to be have cursed the language in a way.  So there were a million ways to do OOP and that ended up with egg on the Perl face.  Now that has been taken care of by Moose.  But the underlying problem seems to still be there.  There are many ways to get things done in Perl, but how does one know the best or ideal way?  There is no mechanism to provide this information to a new or old developer.

I think the Perl community is realizing that they need to change some things around.  This is healthy regardless of the language.  I don&#039;t think it&#039;s too late for Perl, it has such a following.</description>
		<content:encoded><![CDATA[<p>I&#8217;m also a Perl dev.  I&#8217;m love Perl but hate some of its issues.  A common Perl saying, &#8216;There&#8217;s more than one way to do it&#8217; seems to be have cursed the language in a way.  So there were a million ways to do OOP and that ended up with egg on the Perl face.  Now that has been taken care of by Moose.  But the underlying problem seems to still be there.  There are many ways to get things done in Perl, but how does one know the best or ideal way?  There is no mechanism to provide this information to a new or old developer.</p>
<p>I think the Perl community is realizing that they need to change some things around.  This is healthy regardless of the language.  I don&#8217;t think it&#8217;s too late for Perl, it has such a following.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

