Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

Let's face it, Perl *is* a scripting language 3 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.

  • Why exactly is C supposed to be better than Perl for large systems (ignore speed of execution, assume that both can in principle satisfy your requirements)? What large-scale development advantages does it, as a language, have? What if you had raised an incredulous eyebrow and asked this gentleman, "you write large systems in *C*???" What would his response have been?

    It's kind of the thing I (try to) have in mind when I hear the word "enterprise". When a system gets big enough and lasts long enough, the

    • I agree, writing large programs in pure C is nuts. Writing large systems in anything that doesn't have automatic garbage collection, is nuts. OTOH other people argue you should only use a strongly typed language for large systems. So, we can't all agree. :)

      Despite the fact that he dislikes Perl, I largely agree with this guy [caltech.edu]. (I don't remember who pointed me to that article, it could easily even have been you (Ovid).)

      Anyway, if you define "system" as something that is really big, then I strongly feel that C is one of the worst choices of a language to program in. If, OTOH, by "system" you mean device drivers and the like, stuff that talks to hardware, then I think C is a good choice.

      It all depends on what you mean by "system".

      • Despite the fact that he dislikes Perl, I largely agree with this guy.

        Thanks for the reference to that excellent article, (Scalable computer programming languages) [caltech.edu] by "this guy" (Mike Vanier).

        Given that he dislikes Perl, I noticed a couple of glaring omissions:

        CPAN doesn't even "come close" to Jarballs?

        Java libraries are wonderful, but no mention of CPAN anywhere in the article.

        Julian Morrison sent me this email:

        There's a very important feature you missed, and it's the real explanati

Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.