Given the above, has anyone have any POSITIVE experiences with either the java-like scripting languages or the java-script desktop scripting languages?
I've experimented with Groovy and Jython in Java/Scala and found both pretty straightforward to integrate. Especially Groovy if I remember correctly. I also liked Groovy in a JVM environment because it was a very Java-implemented way of doing things.
posted 6 years ago
Thank you. Groovy sounds like a good choice. Do you know if you can do something like force a "strict" syntax so you don't get into the habit of using it's admittedly nice syntactical sugar.
Gary Furash wrote:Thank you. Groovy sounds like a good choice. Do you know if you can do something like force a "strict" syntax so you don't get into the habit of using it's admittedly nice syntactical sugar.
Also, there is nothing in principle to stop you mixing Java and Groovy code in your project, as well as using it as a very flexible stand-alone scripting tool that still gives you direct access to the full power of Java's libraries. And Groovy is also the basis for the excellent Grails web application framework (think Rails for Java). One other perceived advantage of Groovy over JVM ports of other languages such as Jython or JRuby is that Groovy is an "indigenous" JVM language, so you know you're always dealing with the definitive implementation. And the name is much, well, groovier...
For a quick intro to the benefits of Groovy for Java developers, check out Ken Kousen's video on Improving Java with Groovy. And give Groovy a try - I'm sure you won't be disappointed.
No more Blub for me, thank you, Vicar.
posted 6 years ago
You won't get any argument from me on the quality of Groovy and it's niftyness as a language. I helped some time back (3+ years ago) with testing and docs (once, but it was still fun). But, I haven't really seen it used since then nor heard as much about it in the marketplace. It's good to know it's still popular.
I'd only use "strict" because I'd just want to avoid "bad habits" when I have to do my java (e.g., using the easier syntax and waiting for an error in my IDE).
No argument on Groovy itself though, and you're probably right that the limited number of syntactical differences won't screw up my normal programming.