in reply to Re: From PHP to Perl - Should I, and how?
in thread From PHP to Perl - Should I, and how?

++ on Template Toolkit. That's a big reason my company hasn't moved to something else (We're a fortune 500 that uses perl internally for almost everything). CPAN is another - being able to install and update libraries is great. We use CGI::Application instead of Catalyst, and I'd probably suggest it instead of catalyst for someone starting out, but both are perfectly capable.
  • Comment on Re^2: From PHP to Perl - Should I, and how?

Replies are listed 'Best First'.
Re^3: From PHP to Perl - Should I, and how?
by locked_user sundialsvc4 (Abbot) on Mar 10, 2009 at 16:56 UTC

    Say... does that mean you're hiring?   Contact me...  :-D

    Actually, I don't have any Catalyst apps out there right now, either. I quoted it because it's got a very large and very diverse list of add-ons right now in CPAN. A very good demonstration of just how much you can do, within one framework, and still be totally “within Perl,” and “within just one (of many) framework(s) within Perl.”

    I can't think of a better demonstration against:   “this is the one-and-only PHP, and therefore all we've got to work with is this one-size-fits-all, so we gotta figure out a way to make this thing work somehow.”

Re^3: From PHP to Perl - Should I, and how?
by salazar (Scribe) on Mar 10, 2009 at 13:23 UTC
    Thanks for pointing that out, I'll be sure to look at that as well. I was enticed by the 906 results on CPAN ;-).