Link Details

I don't understand why so much fuss on Java, -java the new cobol- -java is dying- -java is sinking... and so on, GIVE IT A BREAK!!!!, stop filling up blogs if you think Java is dead. Don't repeat or forward links over and over the same news, move forward, write/learn something useful if you think JAVA couldn't make it up to your needs.

Berlin Brown is a pretty thoughtful writer, and I didn't feel his opinion was a mere rehash of the same old complaints others are making. Still, I do agree that this dead horse has probably endured enough whipping!

Thanks Rick.

One of the reasons I wrote this was because:

1. I now work with COBOL developers. We are writing the web frontend to COBOL/Mainframe backend (Financial Services). I sit next to Java and COBOL developers. And I ask the question about what they feel about COBOL, what they feel about Java. (Sometimes how they feel about Python based apps) I didn't really convey it that well (because I don't code in COBOL), but COBOL wasn't really designed as a robust general purpose language, wasn't designed for the demands of 2008.

With that being said, the same thing could happen to Java (or is happening). Java/J2EE has gained a massive following over the last 10 years. Will it receive the same kind of response 10,20,30 years into the future.

As a developer, I get asked to work on a variety of different projects. Time and time again, I see new tasks that will take a greater amount of resources if we use the plain-jane Java methodologies and libraries. Less resources with other programming languages. But, this doesn't necessarily mean that companies and developers have to immediately jump ship and convert all projects to X language or Framework. They should look at the technology that is out there and look at resource allocation. The typical attitude is to just throw more java libraries at the problem (it might be DWR or GWT for Ajax support). Sure, the managers have to look at training and network architecture and all of that; but it isn't like it can't be done and the evolution of a newer system may create some interesting results.

2. Second Point: I hate the way that writers/bloggers frame the "Java is the new COBOL" argument. It gives the impression that Java is completely dead and make sure to choose Rails as your alternative. This isn't the case. There is certainly an advantage to J2EE development and Java will probably remain around for a long time, just as COBOL has survived for so long. But, I don't believe Java is always the best choice for new requirements (Mashups, Ajax Widget Toolkits, Semantic Web, etc, etc) especially considering that new languages have a strong community and rich set of libraries. Ruby/Rails, Python/Django, Erlang, on and on.

Maybe I didn't express it like I wanted to (I spend more time coding than blogging), but I really wanted to make those two points.,

"There is certainly an advantage to J2EE development "

J2EE has some advantages.

Please give up on the why Java is like-or-not-like COBOL. I don't know how this all started but it's sooooooo old already. Authors of articles of either kinds, like or not-like, lose so much credibility arguing moot points.

If java is going to die, then, who will get the most benefit?
1. C#
2. M$
3. Ball... Bill...
4. all of above :D

It doesn't mean Java is going to die. There are some firms that have thousands of Java developers. But it might remain stagnant and not receive much new developer interest. Just like COBOL. You don't see new and exciting techniques for COBOL development. Struts2, Hibernate and a lot of other J2EE libraries make some aspects of Java development easier but how much can these libraries grow?

"You don't see new and exciting techniques for COBOL development."

New, yes, exciting, no. IBM put object orientation into Cobol back in the 90's. It's the most disgusting, verbose thing you've ever seen. There are 20 million + LOC Cobol apps that have been running every business day for 40 years. Is Java there yet? The comparison is ludicrous from that perspective.