Path::Dispatcher: a dispatcher that can work just about anywhere. It works (roughly) analogously to the way mod_perl works when matching URIs and dispatching to URI handlers. This code can work in any context including the command line.

These really aren't that recent, but I just discovered them. They also aren't 'talks' (well, they were talks, but the talk itself was not recorded), but, instead, slideshows. Nevertheless I found them all interesting.

I've been using DBIx::Class recently. It's the first ORM I've ever used and it seems seemless. Here is a slideshow introducing DBIx::Class. Another detailing the much newer DBIx::Class::DeploymentHandler.

Plack is another interesting platform I've been unable to use as of yet. But here is a slideshow that has some very impressive example code.

About 6 or 7 months ago I noticed I was being indexed by a search engine named Duck Duck Go. I went to the main page and it seemed interesting, but I never went back. Today I read that Duck Duck Go is written in Perl. I still don't know that I'll start using Duck Duck Go, but I find it very interesting that what is likely a very large project is using Perl. People who talk about the lack of scalability of Perl or the poor performance of Perl should take notice.

I agree with this post very much.

I think this is exactly right. Knowing about perldoc and how to use perldoc is very important to becoming a good Perl developer (and, really, learning the documentation system for any language will be important). Two things that are not mentioned in the article are the '-m' and '-l' arguments. I use '-m' every single day. It is very useful for quickly viewing the code for a module, and, thus, it is a useful tool for seeing how others have solved particular problems. '-l' I use less frequently but it is useful for finding the absolute location of the module on the file system.

IPC::Run3: the successor to IPC::Open2. A simpler API with the same functionality.

Ever wondered about Perl modules that would help you build a dependency tree in a manner similar to make? A recent PerlMonks question was also curious. Only one answer (so far) but the question plus the answer have some interesting ideas.

The answer suggested cons. cons is a very old system and I had not realized it was still active...and based on the e-mail archive, it isn't. The FAQ was last updated in 2001. This would not likely be the first place I would look.

The question itself mentioned two modules that I was unaware of: Algorithm::Dependency and Decision::Depends. The former appears to be the module with the most recent update, but the OP seems to have chosen the latter to help him solve his problem.

I've never used Plack but I've read a little about it recently. This seems like a good place to start if you want to learn more about how to use it.

Config::Model: A framework for creating configuration validation and editors. This is something I've wanted to write for awhile now. If I understand the goal of this module correctly it should make writing configuration systems very simple.

App::perlbrew: Manage perl installations in your $HOME. I can see where this can be very useful. Here is an introduction on its use.

I've often noticed that assigning to $0 on a Linux machine doesn't always do what you think it does. This may fix that.

In a followup to a previous post (on which I also commented) John Napiorkowski points out that it appears Google is now doing the right thing. I didn't find the reddit thread quite as informative as he seemed to, but the Google Groups discussion is a good, quick read.

Moose: It looks like version 1.0 of Moose has finally been released. I don't use Moose and my initial introduction to Moose (over 1.5 years ago now) was not a particularly positive experience. Having said that I would say that this is a pretty big deal. It seems a lot of people really like Moose and I think that sometime in the near future I may jump on the Moose bandwagon.

Acme::Module::Build::Tiny: A tiny replacement for Module::Build. Written by the same author who maintains Module::Build. It is missing a lot of features, but if you don't need those features this module is very light.

Scope::OnExit: Execute code on scope exit. I'm not certain when I'd use this, but it looks useful for theoretically interesting things.

I don't have an iPhone, but this does seem pretty cool.