Link Details

And how many "killers" will there ultimately be? I'm wondering whether we should set up a community betting pool on this one!

Scripting isn't always the answer. Sure, scripting languages are less verbose, which makes you more productive. However, it's only like that as long as it's something small. At some point it starts to look messy and it gets less maintainable. Scripting languages are really awesome for wiring things together though.

So, yea... I basically fully agree with him. ;)

I think it's delightful and refreshing with how the dynamic languages and .NET have been able to push Java a little out of its beauty sleep. And what a boring world if we did not strive for better tools, libraries and languages. Even Joshua Bloch and James Gosling have been caught on tape admitting that the reset button should be pushed. Java is great, but its greatness is slipping slowly but surely as more and more hacks finds its way and the required skills to use it goes up. The killer of Java 2 would be nothing short of Java 3 or an open sourcing of .NET, that's where I'd place my money.

Ruby developers are killing Java with all the propaganda they are doing. All they do is blog about how much Java sucks. They master the propaganda technique and they are trying to convert as much Java developers as possible by writting millions of posts, and spread the love using sites like DZone, but when you visit their sites, the love becomes hate. And that's when they tell you how much java sucks. Hey, they've told me that so many times that I'm starting to believe them. Propaganda? Oh yes, it works!