I tried this example for BerkeleyDB:

http://forums.oracle.com/forums/thread.jspa?threadID=594269&tstart=15

and the tail-recursive printAll function causes a stack overflow.

I’ve been asking to my workers to keep an open mind about scala, but I keep running into compiler errors like the above that are breaking my trust.

I kid, I kid. A little.

I’ve not really looked into it deeply. My impression is that for most usages Scala and Groovy are comparably expressive, but they push in different directions as you start to (over?) use their advanced features.

Looking at e.g. the groovy cookbook examples I don’t see it as being any better than Scala when using existing APIs. You’re just too tied to the way of thinking of the API to really break away from it. In both cases you need to wrap things and write your own small APIs to make things more palatable.

Beyond that, I don’t have much to say. I’ve not looked at Groovy in any significant amount of detail.