Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

leedo (8228)

leedo
  (email not shown publicly)
+ -

  Comment: loop variable (Score 1) on 2009.12.06 18:07

by leedo on 2009.12.06 18:07 (#71328)
Attached to: Template::Tiny 0.01 - Request for features
The one thing I am missing from TT while working in Text::MicroTemplate is the loop variable. It lets you check what the loop index is and has a few convenience methods, such as loop.first. http://template-toolkit.org/docs/manual/Variables.html#section_loop
Read More 10 comments
Comments: 10
+ -

  Comment: Bit me the other day (Score 1) on 2009.09.29 10:19

by leedo on 2009.09.29 10:19 (#70688)
Attached to: Multiple Inheritance and Exporter
I maintain an ancient codebase (uses Class:DBI and Exporter heavily) and ran into this recently. I had a hell of a time tracking it down and ended up just fixing it by not inheriting from Exporter. It was all pretty frustrating.
Read More 4 comments
Comments: 4
+ -

  Comment: Worth using either way (Score 1) on 2009.08.12 10:17

I don't think git is going to magically draw more contributors to a project, but it certainly does make the lives of everyone involved with the project easier.

Even if you end up with the same number of contributions when compared to svn, I still think git is worth the switch. Being able to add a remote repository and cherry-pick a specific patch, or merge a branch in a matter of minutes is great. I don't maintain any popular projects, but for the few that I do get contributions, it has made my job much quicker and simpler.

Read More 24 comments
Comments: 24
+ -

  Comment: YSlow FF plugin (Score 1) on 2009.07.28 23:01

by leedo on 2009.07.28 23:01 (#69747)
Attached to: Improving perldoc.perl.org load times
You probably know this, but another traditional approach is to put the JS files at the end of the HTML doc. The YSlow Firebug add-on probably has some other good tips.
Read More 12 comments
Comments: 12
+ -

  Comment: Don't just market the language (Score 1) on 2009.07.28 13:48

As much as I think a more a uniform style and message would be great for Perl, I also think that releasing and marketing an application that non-Perl people would find cool and useful could do as much to fix Perl's image problem as anything else.

After using this fictional application, a user might see that it is written in Perl and think "Hey, I didn't know that Perl can do that". They might then look at the source code and think, "Hey, this isn't the same ugly Perl that I remember from the mid 90s."

A good example of this for me was Rails. When Rails was released I didn't know much about Ruby, but that one project prompted me to look into the language. It wasn't the marketing coming out of the Ruby camp that inspired me so much as the cool things you could do with Rails and clear messaging on the Rail's website.

Read More 36 comments
Comments: 36
+ -

  Comment: Good luck (Score 1) on 2009.04.22 10:28

by leedo on 2009.04.22 10:28 (#68238)
Attached to: Beautiful is better than ugly
I would suggest that use.perl.org is the worst of the bunch. Frankly, I am embarrassed to share links to here with my friends. When I do share a use.perl.org link, I inevitably get a comment back about how ugly and unusable the site is (particularly the comments.) I think the problem is just a general apathy towards good design in the perl community. It is too bad, because it is not something people can learn to appreciate overnight.
Read More 73 comments
Comments: 73