Go ahead and try Groovy in your new project. At the very worst, you
will have to port everything you did to Java, which is easy enough, and
not likely to happen. At the best, you will find that most everything
you do can be written in Groovy and be performant too.
How is that possible?
Most of the code that actually runs is already written in Java! You are
using JBoss. Big honkin application. Lots of functionality. Just
about everything you will do in Groovy is going to be a method call into
some JBoss code. Most of your time is spent in the JBoss code, not in
the overhead to call a single method.
If you run into a piece of code that needs raw performance (i.e. - a
binary tree, finding prime numbers, or God forbid, needlessly iterating
a counter a million times), by all means, do that in Java. And if you
need a binary tree, use a TreeMap. :-)
Visual Basic was an interpreted language through version 4, and despite
it's rather glaring design flaws and the limited hardware of the day, it
became wildly popular (because most of the "hard stuff" was written in
C++). It became popular because it made things so much easier. 'Nuff
said.
Jason Smith
-----Original Message-----
From: fangzx [mailto:
fangzhouxing@...]
Sent: Wednesday, December 26, 2007 6:42 AM
To:
user@...
Subject: [groovy-user] groovy is slow
I have read this article 'Why is Groovy so slow?':
http://www.jroller.com/rants/entry/why_is_groovy_so_slowI planed to use Groovy in my new project based on JBoss Seam, but now I
must wait.
Can anyone give me some advice?
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email