use Perl

I didn't look hard for these -- just found them on the first page of Google results. The names are here.

I had no trouble finding hosting that supports mod_perl for $30/month, but people who are really broke will probably use FastCGI, which I found for $6/month. I can't see costs this low being a barrier for people.

If you search PerlMonks for things like "cheap hosting" you'll see a lot of hand-wringing about PHP and people describing this as a mod_perl problem.

What you're saying about ease of getting started with PHP is true, and personally I'm not interested in fighting that battle, but people who are should probably work on getting Mason included in the perl core. It runs fine on FastCGI and delivers a similar experience.

I keep seeing people refer to some kind of crisis in the world of cheap Perl web hosting. They talk about ISPs not supporting mod_perl and invoke PHP as an evil horde conquering all hosts.

Well, I'm fine with PHP, and congratulate it on its success. However, Perl is not in trouble.

I wasn't trying to be insulting. It's only reasonable to look for user mistakes or misunderstanding before assuming that a behavior in a widely used piece of software is a bug. Think of how many times people have reported they found a bug in Perl and how many times they actually had.

I suspect there's an answer for this one involving either how the paths under CWD are figured or which revisions are shown when no number is specified. If you actually want to solve it, I suspect you'd be better off asking on the svn list.

Sorry, but svn log -v works. You're either not looking at the code or you didn't commit a delete on the file.

Just curious. I usually try to arrange them so that most calls to other subs in the same file are forward references and the internal subs are defined close to where they are called most prominently. Does anyone else think about this?

You don't need to dedicate a server to running a different apache. You can run as many different apache/mod_perl binaries as you like on a single machine.

If you haven't seen it yet, CHI is the new replacement for the nice-but-slow Cache::Cache modules. I uploaded a DBI driver for it to CPAN. If you're skeptical of the value, try benchmarking MySQL against memcached. It's pretty close for this kind of thing, and on a local connection MySQL wins by a fair amount. It's also a lot simpler than trying to get memcached or Cache::FastMmap going on some random shared hosting provider.

I don't like File::Find::Rule at all, and everyone seems to have their favorite. At least I know I can make File::Find work reliably, even if it's clunky.