Link Details

I've said it before. Let's stabilize the language and focus on improving the plaform (VM and libraries).
If the language is weak in a certain area or another language is better for a task, then use the other language and compile it to JVM bytecode. This gives the ultimate flexibility and re-use while controlling complexity. If Ruby/Python/Scala/etc is better at something, then use it with jRuby/Jython/whatever.

If we try to have an uber-programming-language to please everybody, then EVERYBODY will suffer.

That is what I would like as well. Time to clean up the house a bit. Focus on getting the most VM performance you can, multiple vm loading. I would really like them to make it a bit more modular. Deprecate stuff into .jars that can be included if old functionality is still needed.

I second that. Use right tool for the right job, don't make a big fat tool which can do bit of everything but you can't pick it up well.

We cant use other languages. These are simply not allowed. For example, one argument against other languages is that there are not enough programmers in other languages. But i want to use closures and other good features. If we can get these things in next version of java, then we can upgrade and say to managers that this is as normal upgrade as always. Then we can finally start using closures for production.