in reply to Killer Apps in Perl?

To say that there's a "killer app" for this or that programming language would mean that the language has a certain "specialization" that makes it uniquely suited to a particular use. But I don't think this works as a design goal for any major programming language.

It's true that one language will have advantages over another in terms of particular features, but these mostly relate to the effectiveness and sanity of programmers, rather than the range of functionality (the "apps") that can be accomplished. Also, the features that are "better" in one language are usually offset by others that are better in the other -- e.g. greater run-time efficiency vs. faster development/prototyping.

But I'd have to say that the first two replies on this thread are totally correct. Perl is an application that is platform independent, and provides users with a degree of power and flexibility that is hard to beat. And CPAN -- especially CPAN.pm -- is something quite unique: an intelligent, easy-to-use tool that really delivers the promise of re-usable code (a stark contrast to, e.g., the "dll hell" of MS-based C++ apps; I always wonder how many functions, in how many different dll files, were written independently to do the same thing... or try to do the same thing, but fail in their various independent ways.)


Comment on Re: Killer Apps in Perl?
Re: Killer Apps in Perl?
by crenz (Priest) on Aug 04, 2002 at 18:40 UTC

    To say that there's a "killer app" for this or that programming language would mean that the language has a certain "specialization" that makes it uniquely suited to a particular use.

    Well, I do think it worked for PHP -- somehow, PHP for a lot of people really caught on as the thing to write dynamic webpages in. And while some people also try to do system admin and cron stuff in it (you will recognize the beginner by seeing commands like 'lynx -dump http://mydomain/script.php' in his cron table), (fortunately) it is mostly limited to the web right now.

    I never quite understood why -- I guess if PHP would not have the '<?' and '?>' tags, but would per default work like perl (ie., use an extra module/different workflow to embed code into HTML), it would not really have caught on.