Originally posted by Prad Dip:
Groovy experts and authors suggest to have many classes one in a script file for performance reason. This is because groovy parses the entire script file before the code gets executed and classes in the script file are more easily availble than when put in another script file. So we do we organize code - Doesn't script file bloat ?
Originally posted by Peter Johnson:
How much was Groovy influenced by Ruby?
Groovy was influenced by a number of languages. I see that following order (most influence first) :
* Java, because that is what we rely on and integrate with
* Perl (especially when it comes to what we try to avoid)
* all the other languages that the devs have ever worked with
Are there problems that are more easily solved in Groovy than Ruby...
Everything that requires tight Java integration, like using Java frameworks that rely on annotations or generics, writing an EJB, extending abstract classes that may have overloaded methods, cross-language refactorings, and so on...
...or the other way around?
When outside the Java platform, Ruby can start up faster which makes it better suited for writing quick-starting scripts like textmate bundles. With Groovy, you typically have a startup-delay of one second or so because of the JVM.
Other than the fact the the JVM provides a much better runtime, what are the advantages of using Groovy over using Ruby?
* leveraging existing Java knowledge (if any)
* using existing Java frameworks and components
* seamless mix&match of Java and Groovy implementations
I guess you see the pattern ;-)
If Java is of any value for you, then is Groovy. If you work in a total non-Java shop, then Groovy provides no benefit for you and you may take Ruby, C#, or whatever else.
Originally posted by Curt King:
I am a bit underwhelmed
Cool wording ;-) Hits the nail on the head.
I'm afraid there is no better solution for eclipse that I know of - but I'm only a very sporadic eclipse user.
What about trying a new IDE on a long afternoon?