Well, I can share a bit. I do not use perl for web development. I use PHP. I love perl, for everything except the web. I have tried mod_perl, python and ruby, but PHP just seemed completely geared to making web pages and making them easy to develop and maintain.

From my perspective there aren't many things that a web language has to have. It has to have great database access (and that's why I use adodb in php). It has to be able to set/get all the variables (cookies, sessions, system, get, post etc..) that are available in a web environment in an easy way. It has to be modular. I could give mod_perl another go because I haven't given it in a go in 7+ years and I'm sure it's a lot more mature, but why? I have yet to run into a problem writing a web page in PHP for a solution.

The command line is an entirely different matter. And I will cry big tears if I'm forced to leave PERL for my ETL work for some fly-by-night language. In fact, my company told us once that we had to use Java. We spent time and energy writing our applications in Java, but in the end we convinced management to allow us to switch back to Perl. I don't want to get into a !java discussion, but let's just say that I didn't find it to be geared to command line ETL work.