All the Perl that's Practical to Extract and Report

Navigation

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
Without JavaScript enabled, you might want to
use the classic discussion system instead. If you login, you can remember this preference.

Please Log In to Continue

I, too wondered about the absence of Larry Wall. He writes wonderfully, and his answers to those questions might provide some insight.

That said, the author of the article says "Not everyone responded to my e-mail, not everyone agreed to answer the questions". Given that, do we actually know who was asked?

Secondly, I may be reading what you wrote unfairly, but it sounds like the primary reason that you want to promote Perl is so that you have job security and don't have to learn other languages. While I certainly have selfish reasons for promoting Perl, I'm not sure if they're the best way to do it, and they're not my only reasons. People should use Perl if and when it's appropriate to what they're doing and it will help them.

Promoting Perl past that would be a disservice, I think. An author of severely-memory-constrained embedded firmware might try using Perl and saying "This sucks!" And they would be right, because a hammer is horrible at tightening screws.

Rereading my comment, I'm concerned that I came off differently than I intended. I did not mean to call you selfish, as I've seen plenty of examples of your generosity. I appologize if I came off as insulting. That was not my intent.

Rather, I meant only that there are reasons to promote Perl that benefit more people at the same time. I want people to use Perl because it helps them, and if it helps me too, well that's awesome.

*laugh* - yeah, job security is great stuff! My uncle's 60 and a COBOL programmer who has reached the end of his shelf-life.:( I've personally seen what the end of the road looks like and it ain't pretty.That said, I agree - Perl isn't for everything. Device drivers, firmware and low-level foundational pieces aside, when you're faced with an algorithm problem, you should be able to use the language you're most familiar with.

For example, I took a look at the first practice room problem in TopCoder, which