On Sun, Feb 24, 2008 at 4:25 PM, Brian Schlining <
bschlining@...> wrote:
> ...However, I use Groovy for
> writing complex 'buisness' logic against databases. About 90% of the
> application time is spent in database calls; so basically it doesn't matter
> how fast the language is. The amount of development time I save for
> writing in Groovy is worth the performance hit; Groovy is more than fast
> 'enough' for my application.
>
> I'm not dismissing the fact that Groovy would benefit from optimization. But
> it's a young language and progressing rapidly. I'm optimistic that
> performance will get much better in the near future. --
This is really the key. Nobody will try to assert that Groovy is
blazingly fast, but it gives _the_best_ productivity if you have a
heavy Java foundation and you want the benefit of a dynamic language.
I have never bothered to look at the benchmarks for Groovy; I just
started using it and I have never had a problem with performance for
anything I've used it for. Isn't that what's important?
Not to mention, as many people pointed out, that speed is a priority
for the language and the coming months are going to show great
improvements in those numbers.
-Tom
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
