Apparently, though unproven, at 03:32 on Sunday 02 January 2011, Stroller did opine thusly:
> On 1/1/2011, at 10:34pm, Grant wrote: > > ... > > I'm starting a new project that is quite straightforward and will > > interface with an old project. The only point of contact between the > > two projects might be both of them having access to the same database > > table. The old project is written in a language that is related to > > perl so I can imagine there would be some benefit to using perl for > > the new project. Am I foolish to start a new project in perl at this > > stage in its lifecycle? I won't be doing the coding myself and I > > wonder if I would be better off with PHP since more coders seem to be > > familiar with PHP than perl. > > I'm not sure if I've mentioned before, but I picked up Perl fairly recently > (within the last 12.5 months) although I haven't done *that* much with it. > > I *really* like Perl. It feels extremely robust and "right". My 2c. I had a similar reason for picking up Perl. Here's what I now think of it: Any language has good coders and bad coders using it, there's nothing the language can do about that and it can't defend you from yourself either. There is much bad Perl code out there but that's because there are so many coders using it. The clincher is: If you are the kind of coder who is pedantic about writing stuff "correctly", Perl goes out of it's way to help you do that. It will also help you to write utter complete shit code too, but that's a human issue, not a language one. -- alan dot mckinnon at gmail dot com
