For some reason, the Java mindset and Perl mindset collide frequently.

Could it be that they're both used for web programming (CGI vs. Servlets/JSP/EJB, et al)?

Next i suppose we will start debating about compilation vs. interpretation ... but i think it really boils down to personal taste.

Don't get the Java guys started ... They live in a doubly-glass house: not only is Java strongly typed (frequently necessitating lines and lines of code to do what can be done in Perl in several or less), but it is BOTH compiled AND interpreted (unless you run on a machine with byte-codes as its machine language, in which case it's still compiled).

Don't get me wrong; I LOVE Perl and Java. My philosophy is "whatever works"; sometimes perl makes sense, sometimes java, JSP or EJB (and sometimes even -- gasp! -- ASP). When any one makes as much sense as the next, then I tend to choose Perl, just because of the shortened development time. And in that (personal taste), I think we probably agree.

dmm

Just call me the Anti-Gates

I think the best way for me to describe Java vs. perl
programming for me is this: in Java, there's probably
only one *best* way to do something. In perl, there
are many ways of doing something, depending on what you
know how to do and what you really want. It's an
embedded dynamism that makes perl very flexible.

Rob

The very flexible nature of Perl is both it's boon and it's bane when compared to Java. True, Perl might be better suited for small tasks and Java better for large projects. Type safety is a must when dealing with large teams of programmers (and have the nay-sayers even seen Class::Contract?) , but what most fail to understand is that once you strip away your frameworks, environments, and containers, what is left? Data munging. Perl is quite good at that, better than most.

The idea of a programming environment independent of language is quite appealing to me and others. They just don't want Perl to be allowed to play in the sandbox. What i don't get is, what is so threatening about Perl? Why not use C# or Java to contain Perl code? Sounds like a powerful combo to me, because both languages lack Perl's raw munging ability. Are there any other languages that provide autovivification besides Perl?

And on a sad note - i recently found myself in an argument with an old friend regarding C#. After he insulted me (and this site), i decided to end our 7 year friendship. Sad. I actually think he was simply trying to lure me into working with him at MicroSoft, but he chose to badger me instead of politely inquiring.

My lesson? Just say 'no thanks' and move on.

jeffa

L-LL-L--L-LL-L--L-LL-L--
-R--R-RR-R--R-RR-R--R-RR
F--F--F--F--F--F--F--F--
(the triplet paradiddle)

Your post is content-rich; I don't know where to begin...

First, I've noticed that any-sized projects can be in
any language, as long as the team is very small and
has a very low turnover rate... so then, perl can find
a niche in very large projects, but it's limited by
the business environment, perhaps.

Second, if perl were embedded into Java... I don't even
know what I'm saying -- if perl and Java were somehow
combined in an unholy matrimony... if it could be done
successfully... I would be ecstatic. I've noted that
Java really does lack things that perl takes for granted,
such as the regexp package (ported to Java, but it
doesn't give the same feel, does it?). And of course,
Java is static. That's a new distinction in my mind,
and I haven't fully realized its impact on my world.

And finally, the maybe-soon-to-be-ubiquitous-or-soon-to-die C#.
Have we all read Mr. Cringely's articles about that?
http://www.pbs.org/cringely/pulpit/pulpit20011101.html
Why does Microsoft sound more and more like some blend
of Disney, Amway, and some funky cult?

Rob