in reply to
Re^2: On the scaleability of Perl Development Practices
in thread On the scaleability of Perl Development Practices
I think you're tackling the problem from the wrong side. You seem to want "I need to write $project_site, what combination of @template_systems, @database_layers, @web_frameworks will do the job best?"
I think it is much better to start by analyzing your project, what it needs, where it needs to go now, and where in the future. If you want to write, for example, a bulletin board, most template systems will work fine for that. But if you know you want extensibility, lots of plugins, and much view functionality in the templates, you might want to start looking at Template-Toolkit rather than HTML-Template. If you want to build a bulletin board thats easy to customize for non-Coders, and don't need any fancy features in the templates itself, I'd go to HTML-Template.
That's why I am usually not interested in surveys or lists of modules people prefer in general. It all needs context. In my experience you can learn a lot by looking at successful projects, their dependencies, and how they use them. And most Perl projects I know are happy to answer "So, you guys used $foo for your project, I'm thinking about using it for $bar, so I'd like to hear how it worked out for you" questions.
Ordinary morality is for ordinary people. -- Aleister Crowley