Groovy or not Groovy?

Looks like things are getting hot for Groovy.

As you might know, Groovy is the latest scripting language on steroids. It contains some nice features such as Closure support, Groovy Markup, Native syntax for Lists and Maps, Regex, … all of these on top of a JVM meaning a great support of Java APIs. Unfortunately for Groovy, the JVM supports plenty of script engines. To be considered a first class citizen, Groovy has at least to be stable and well supported by its community.

  • Given the grammar and parser that it currently uses, it cannot be called very stable.
  • However, support seems to be there with a little lack of communication.

Future is brighter !

For now, I’ll use BeanShell, my favorite scripting language. Why?

  • It cannot be simpler to learn. It uses JAVA 5 syntax.
  • I don’t have to declare type of variables and parameters. It’s the minimum we ask for a fast prototyping language.
  • Easily embedded into existing JAVA apps.
  • I can do things forbidden in proper JAVA, such as have access to private fields.
  • It supports JavaDoc for the scripts.
  • It is stable.

One thought on “Groovy or not Groovy?”

  1. Rome wasn’t built in a day, and it takes time to build a successful language, especially with just a few developers. But things are in a good shape for Groovy. As far as the stability is concerned, Groovy’s quite stable already, contrary to what some bloggers might say–I even wonder if those persons ever used Groovy at all. The community is very supportive and friendly. So, frankly, it’s hot, but in the good sense.

Comments are closed.