Embedded scala vs embedded groovy?

I would not add another language, scala is great for the scripting. Speed-wise I guess scala is typically faster than groovy (there are old benchmarks on shootout.alioth.debian. Org, but somehow groovy seems to have dropped out from the current benchmarks?).

However responsiveness is suboptimal, that is, as you may know, running the "interpreter" used for scala REPL is a compiler that compiles on the fly. This comes with a bit of latency for the actual compilation, but then the execution speed is just as normal compiled scala. On contemporary computers you won't notice this latency any more there are several little tools built on top of the scala REPL, e.g. I made a little swing wrapper using jsyntaxpane ( https://github.

Com/Sciss/ScalaInterpreterPane ), so it should be easy to get going another advantage of staying with one language might be that it gets probably easier to bind symbols to the interpreter, as all scala specific stuff (such as synthetic methods, companion objects etc.) are transparently visible edit: although the original post is from 2009, there are benchmarks from the recent scala 2.8 and groovy 1.7 spread across the comments, showing still a magnitude in difference: stronglytypedblog.blogspot.com/2009/07/j....

I would not add another language, scala is great for the scripting. Speed-wise I guess scala is typically faster than groovy (there are old benchmarks on shootout.alioth.debian. Org, but somehow groovy seems to have dropped out from the current benchmarks?).

However responsiveness is suboptimal, that is, as you may know, running the "interpreter" used for scala REPL is a compiler that compiles on the fly. This comes with a bit of latency for the actual compilation, but then the execution speed is just as normal compiled scala. On contemporary computers you won't notice this latency any more.

There are several little tools built on top of the scala REPL, e.g. I made a little swing wrapper using jsyntaxpane ( https://github.Com/Sciss/ScalaInterpreterPane ), so it should be easy to get going. Another advantage of staying with one language might be that it gets probably easier to bind symbols to the interpreter, as all scala specific stuff (such as synthetic methods, companion objects etc. ) are transparently visible. Edit: although the original post is from 2009, there are benchmarks from the recent scala 2.8 and groovy 1.7 spread across the comments, showing still a magnitude in difference: stronglytypedblog.blogspot.com/2009/07/j....

As far as I know, there was some effort to implement the Java API (Scripting language support, JSR 223) which is necessary to use languages "as scripting languages", but I'm not sure how well that worked out. Scala is overall faster than Groovy, because it stays more closely to the idioms which the JVM can execute fast. But Groovy is really one of the scripting languages for the JVM.

There should be also some support for building Java/Scala/Groovy files together, so that should not create problems.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.