Link Details

The Java language is quite dead.

The platform however is still very much alive. And if you compare the Java community with the .NET community, you will see that much more is going on.

But it is a shame that not many new interesting features are added (especially closures).

All of the complaints are about the API not the language.

On another note, do we really need many changes to the language? I'd rather see more effort on optimizing the JIT and JVM and improvements in the core API. If I need closures, or whatever, I can just use one of the other languages (that runs on the VM) that has them.

this.

The language is fine and the platform is fine. Find me another langauge that is as fast, can be written and runs anywhere, has such an extensive set of open source libraries, and then I'll consider changing. Until then, articles and comments like alarmnummer's are the mental masturbation of supreme asshats.

It's very disappointing but expected. I'd stop caring about Java completely if it wasn't for the fact that many companies sadly prefer standards and stability over productivity and developer happiness.

Oh yes, so sad. As a developer I definitely prefer an unstable language that lacks standards, to a stable, fast, mature one with a wealth of tools, any library you can imagine, and a massive developer community.

@cbang
Our team uses Java and everyone is very productive and happy. What's your point again?

I still think the author has a valid point. To me, a release without closures does not make any sense.

Everybody writes loops, every day. Since the advent of spring, really few people open files by hand. I think the JDK team needs some focus.

No he doesn't. It's self serving clap trap. Closures are not that important.