Re: Perl vs Java - your feedback, not flames

Raj Mathur wrote:
>     Nishi> - App is -- extremely search intensive -- extremely complex
>     Nishi> algorithms to be used on server side -- no room for slow
>     Nishi> interface
>     Nishi> Personally, I am inclined towards Perl because
>     Nishi> - it has a faster turnaround time i.e. code, test, and code
>     Nishi> again. No compilations.  - with coding standards in place
>     Nishi> and 'must document' policy, code complexity, and obscurity
>     Nishi> can be minimized.  - it is easily/everywhere supported by
>     Nishi> all ISPs. ISP offering Tomcat is hard/expensive to find.
> 
> What I like about Java:
> You have
> decent IDEs that can parse your classes and make life easy for you.
Infact the Perl Plugin for Eclipse is also very good.
See http://e-p-i-c.sourceforge.net/
> - - Speed.  Man, that really sucks.  I've seen large, multiple-CPU
> systems crawl to a grinding halt when running complex Java code.  
Between various JVM's I found that successive JVMs have bettered the
performance and so have successive versions of Tomcat.
As of today I find server side java code to be normally faster and more
responsive than perl-cgi. What is the opinion of others? 
> But no, you have to manually promote the int while
> bloodying your head against the wall and cursing the Java designers.
Its irritating and its by design ;-)
> - - Namespaces.  In Perl I can conditionally import library methods and
> functions into my main namespace.  That's just not possible in Java.
> I find this most restrictive when defining utility functions -- to
> access those I have to instantiate an object of the utility class and
> call the method from that object.  WTF?
Just curious why would you want to do that. Why not use a import static?
In any case the Java namespace is much cleaner with the convention of using
a domain name to start your functions.
-Tarun
-- 
http://www.tarundua.net
Nothing you ever wanted to find about Tarun Dua