Bruce Eckel says at artima.com; 

But we need to become especially conservative when considering major, fundamental language features like closures which, while they can be very appealing in theory, may have a cost that is too great in practice when they are forced into a language that values backward compatibility over the clarity of its abstractions.

I am a traditionalist.  I live and breath the Java language since the days of Java 1.1 back in ’97.  I have seen the goods and bads of the language and devised ways to best implement things despite Java’s shortcomings.

Just like my stand regarding additional functionalities to the language, I’d rather opt for the traditional ones.  It’s not that features added since Java 5 were bad, my point is, the vast majority of Java code in the wild is still written in the old way, and sadly and I bet, in a primitive newbie-like way.  Introducing new features to the language will just dilute developers’ attention and logic-formulation.

Just my piece of mind regarding Java…

Powered by ScribeFire.