According to me the disaster has already occurred. The only section of programmers using Java day in and out for their projects are low price substandard developers who can't write a line of code without the IDE doing autocomplete at every key stroke.

Coming to Android and other Google initiative they tend to happen only because the tooling, documentation support and a large pool of programmers that exist.

Java today is not used because its awesome, its used because for a certain section of industry needs massive supply of low price programmers. And with Java the people, the tooling support and rest is already there.

Hence no doubt Java is the next COBOL.

I do Java in my day job and I agree, I couldn't write much Java code without an IDE, mainly because Java is a horrible language to cut code in and you do need to write a lot of boilerplate for many Java EE patterns.

The IDE removes that problem somewhat.

It's not that Java coders "can't write a line of code without an IDE", it's Java coders don't have the patience to write pure Java in a text editor.

You're also forgetting that a lot of enterprise applications consist of many many .java source files for each class. Trying to deal with all of that manually becomes a real headache

I don't know why anybody would create a headache and then try to cure it.

Intelligent people avoid headaches.

Prevention is better than cure. And IDE is a cure, Avoid what forces you to resort to a cure. Prevent the disease itself.

I use a few prog. langs. and still prefer Java in many cases because the tooling is more advanced than any other language platforms.

Thank you for insulting Hadoop, Hbase, Cassandra, GWT commiters and developers at Google, Twitter, LinkedIN, and many more smart people who happened to choose Java.

Nice reply with no factual support.

I don't if its 'chose' or 'forced to choose' by pointy haired managers, mate!

By the way when given the choice its clear what the founders choose. Larry Page and Sergey Brin chose C++ and Python and Mark Zuckerberg chose Php. Twitter started out on Rails.

So its clear the Java mess seeps in only when the hackers are cleared from the scene and the layers of management begin to take control.

Yup, Paul Buchheit was somehow forced to use Java to write GMail with q gun in his head or something. And somehow Twitter engineers was forced to use Java because management said so...

I don't even want to know how you came into these conclusions. They don't make any sense at all.

Java was 3 years old when Google started off. Did you get the link where one of the founders was asking question about Java back in 98 regarding web development? Did you know that Java has been used for many many years inside Google when these so called hackers were still working there?

Did you know that Twitter actually gets more stable when they migrated to Scala and Java? Did you check the presentation by Twitter engineer as to why they moved away? Those are technical presentations, not management business type of presentation. Are you suggesting that rails hackers were the culprit of all Twitter scalability iscsues?

I am unsure if we live in the same world mate.