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.

My programming sifu can kick your programming sifu's ass 1 Comment More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • In your post, you have a few arg's on why Java has problems. IMHO, you weaken your argument when you say things like:
    Java languished for a long time without regular expressions.
    That's past tense - it doesn't matter unless the current set of regular expression functionality isn't stable or as fully-featured. If it is, say that, instead of talking about how Perl was great against Java v1.0 (or whatever).

    I liked how one /. poster [slashdot.org] said:
    The regular expression support of languages like Python, Ruby, and even C# trump that of Perl.
    Can (s)he back that up?

    I guess it's kinda funny (and sad) how both sides flex their "muscles" and slip into exaggerated representations of how good their language is or how bad their non-language is.

    We need to rise above that, keep producing excellent proofs of concepts, and remain true to that great adage, "Other languages don't have to suck in order for Perl to be good."

    Peace,

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