Alex,

This suggestion comes up every year or so in various forms.

I'm afraid my reaction to it is always the same. It's a *really* bad idea.

Firstly it involves inventing a new language. This language has the same syntax as Groovy but completely different semantics. Actually the idea of implementing such a language is not in itself a bad idea at all. Were somebody to set up a separate project to do so I'd follow its progress with great interest. However doing it on the back of the Groovy project is, in my view, a non starter.

Secondly, the history of mixing two languages in one file has a very unhappy history. I have done a couple if implementations of languages which allow low level inserts and I never want to suffer the support issues caused by that again.

Thirdly it lets you off the hook. Groovy performance was awful and is getting better (due, to a great extent, to your good work). Once people can switch of dynamic behaviour to get higher performance the motivation for dynamic performance improvement will dramatically reduce. Groovy's performance has gone from appalling to not so good (an people have produced perfectly good production systems with Groovy's appalling performance). I'm sure you can the rest of the team can move the performance to excellent (you just have to stop trying to fix the unfixable). I am very happy to help as is Charlie (I'm reading the whole of this thread in one go as Nabble has had a Groovy burp and has held all the messages back for a day).

Fourthly you have replaced one problem (how to implement a high quality dynamic language) with two (how to implement a high quality dynamic language and how to implement a high quality static language) If you are having difficulty solving the first problem how does adding a second problem help you?

If the project were to adopt this suggestion I'm of the opinion that you would end up with a combination of a third rate dynamic language coupled with a second rate static language.

John wilson

-- View this message in context:
http://www.nabble.com/Groovy-performance%3A-what-to-do-tp15563866p15570434.html Sent from the groovy - dev mailing list archive at Nabble.com.

--------------------------------------------------------------------- To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email