Groovy++? Ok, so where's the beef?
Update: You can find the sources at http://code.google.com/p/groovypptest/downloads/list
So where's the fracking code?
I can understand a need for control. I can understand the author's desire to turn this into something significant for themselves financially. A man's got to eat. But until the code is open and can be inspected by some experts, I remain skeptical of Groovy++. I am hopeful however that performance improvements can be made given enough manpower and talent. Too bad we all have day jobs ;)
Labels: Groovy
4 Comments:
Code is available at http://code.google.com/p/groovypptest/downloads/list
Yeah, day job sucks! ;p
Anyway, I'm really curious about Groovy++. Not that any of the applications our company has in production really needs any performance gain, but hey, we're all nerds :-)
Thanks for the pointer to the source. I will update the post :)
Kimble: I was actually a bit surprised by the performance results I linked to in the article. I'd love to see some professional testing done on Groovy vs java first.
Post a Comment
Subscribe to Post Comments [Atom]
<< Home