[groovy-user] Advocating Groovy vs. Java
As happens every so often, I'm asked about Groovy vs. Java
performance because I use Groovy in my daily programming. This
comes from other groups that are considering using Groovy for full
server-tier or web-application programming. Does anyone in this
group have any current statistics that can provide performance
comparisons for the latest Groovy 2.3 (or upcoming Groovy 2.4)? A
web search shows Groovy
2.1 vs. Java 7
. I'm hoping this is outdated, because the
results are not great (unless you're comparing them to other dynamic
languages that are even slower).
How significant today is performance on the decision to write
applications in Groovy instead of Java? I'm talking about full
server-side and web applications, not scripts.
I want to best represent Groovy in some upcoming discussions, so
please feel free to share the best arguments for Groovy that
presently exist. Lastly, I wonder if some of these arguments will
find their way to the upcoming Groovy in Action book?
[Thanks to Paul King for letting us know that traits will be
included!] My short advocacy list for Groovy includes:
- Dynamic programming
- Native syntax for lists, maps, regular expressions
- DSLs: builders for json, xml, etc.
- Everything is an Object
- Simpler beans
- Easier to maintain
I'd like to add more to the list and, hopefully, not have to defend
against performance or other criticisms. But, no matter what, I'd
like to know the truth of the pros vs. cons because people aren't
converted when only hearing the positives.
Principal Software Developer, Fraud and Compliance Solutions
SAS Institute, 940 NW Cary Pkwy #129, Cary, NC 27513-2792