Is it time for the Perl community to start focussing on a dominant framework/templating system if only to generate some good books and make it easier for ISPs to have a complete kit installed without too much fuss?

I'd have to say: No. If you ask me, it's time to stop being jealous of what Ruby and PHP have. That's popularity and a broad user base. My main issue with these is that with more people coming it seems that there comes a lower skill level.

What I'd like Perl to focus on is deployment features.

• Independence: See for example the Catalyst framwork that runs on mod_perl, FastCGI a built-in server and more, with enough abstraction to allow new engines to be added.
• Packaging: of Modules as well as of applications, for ease of deployment. Personally, I miss something generic to attach a specific version of a module to an application, if the module is rather critical.

I think Perl is pretty good as it istm, and the Community works because it's filled with passionated, experienced users. I'd personally rather not want a broader userbase to come and lower the average technological level. I like Perl's professional attitude much, much more.

Another point would be: Who should focus? It's up to the users what they choose, and up to the writers what they publish books about. Sure, the writers could just pick a framework, but who says the userbase will follow that lead? It's not that Catalyst, Jifty, Mojo or Maypole are all doing the same thing just in different colors. There isn't *the* framework, but merely a framework for a specific time/person/problem.

The community is vital and evolving on many edges. I like that.