I would like to share my point of view:

Perl really provides many options how to support dynamic web. You should evaluate your motives to choose the proper one. For instance:

If I need to script some simple dynamic page(s) from time to time and I really do not care, what is behind the scene, I try CGI. This is concept very similar to php. Access of the url causes launching of related script.

If I need to code web project, controlling Apache behaviour relatively exactly, but I do not need prefabricated modules, I try pure mod_perl. Access of the url causes launching of related perl module subroutine.

If I need a lot of work prefabricated, something like Catalyst or Mason would be proper choice.

Other dimension is templating. My opinion is that templating (mixing form and content) varies from trivial (simple web service with text or xml output, web API) to complex solution (large webs working with different types of browsers). Trivial solutions can be easily supported by direct print from the code, complex solution needs some mature and complex templating system. I typically operate somewhere in the middle, liking Petal.