Thank you, John, for your comments! As usually it reasonable and well-argued. Please see my thoughts below.

I didn't expect that it is my invention :(

But seriously. I think all of us know the reason. It is not only because of performance (which is very important factor) but also because sometimes people want to have static typing and some times don't. Right now their only option is nice Groovy syntax for dynamic part and pure Java syntax for static. But let me repeat - THEY WANT BOTH

You are 100% correct. I had many discussions with my ex-collegues in JetBrains, who are much better experts in languages then I, I would say who are real experts. and they claim the same - it becomes two languages.

And I agree with that. The question is "is it so bad"? And my answer is "no, as long as we and users understand what and why is going on" Vice versa, I believe there is demand and such approach will fulfill the demand.

You said very right words "stop trying to fix unfixable". But look, do we have real choice? A lot of people use Groovy already and, what is much more important, A LOT of people start to use both Groovy and Grails on their new development or integrate it in to their existing products right now. Should we say to them "hey guys, go forward, but it might happen that in 6-9 months we will give you Groovy 2.0 with new MOP etc., which potentially will be huge breaking change"? I am not sure.

<IMPORTANT NOTE FOR GROOVY USERS> There is no any direct or indirect agreed plans to make serious breaking changes in Groovy language or runtime. As always nobody want to create troubles for users just for fun or to simplify life of developers of Groovy Core. </IMPORTANT NOTE FOR GROOVY USERS>

I believe that there are huge chances that breaking changes will not be huge. The problem is I would feel myself much more comfortable if we had design for so-called MOP 2.0 (I completely agree what existing MOP is suboptimal both in design and implementation), which fulfill just 2 but conflicting requirements - maximal compatibility with existing code - much better performance

Hey, join the team back, show your vision of design and let us implement it if it is great :)

Seriously, yours and Charlie's help is really valuable. It is great source of ideas and experience. At least for me. I don't know the story why you are not involved directly to Groovy development any more but I am really sorry for that. I am sure not only me will be happy if you decided to participate again not only by ideas and expirience but by real development as well. Anyway, thank you once more for all your help.

As I said I believe there is huge user demand for mixed typing. So I don't add new problem but reformulate existing one.

Here I don't agree with you. I believe that we have good chances for high class language with mixed typing.

Alex

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

http://xircles.codehaus.org/manage_email