• Add a Comment
  • Edit
  • More Actions v
  • Quarantine this Entry

Comments (4)

1 localhost commented Permalink

Yes, I must admit that I was also surprised to see this article in BusinessWeek. The whole "Java on the decline" meme has been picking up steam in the past couple of months - a few examples - this article in BusinessWeek (BusinessWeek!) and Bruce Tate's book Beyond Java.I think as always, we need to be pragmatic, and say "the right tool for the right problem". You point out some places where J2EE makes a great deal of sense. For instance, if I need to do two-phase commit transactions across distributed heterogeneous systems, I'm certainly going to look to Java. But as Tate mentions in his book, if you're after the simple ubiquitous use case of "a web app babysitting an RDB", Ruby on Rails (according to Tate and others) is much simpler.The most important thing is not to discount emerging programming languages because of current shortcomings... like any disruptive innovation, at present they may be lacking in functionality and/or performance vs. Java, but over time they're likely to catch up, and if they can catch up without sacrificing too much of their simplicity along the way, they're likely to make Java legacy.As Grady once said (to paraphrase), "I don't believe Java is the last programming language, though it might be for Scott McNealy!".

2 localhost commented Permalink

I'll agree that it's over-the-top to say that Java is passe, but I do think that (as with so many things) there's a grain of truth in there.I've been pointing out in a number of places recently (including http://www.mwdadvisors.com/blog/2005/12/with-sca-reality-bites-j2ee-again-but.html and this podcast: http://libsyn.com/media/interarbor/BriefingsDirect_20051211_1332.mp3) - it's not that Java is in any way "dead" or "passe". But it is becoming increasingly obvious that outside the world of .NET, J2EE specifically is not the only answer.You might splutter at this point and say "who ever said that it *was*?": and the truth is that in the technical community that we inhabit, the reality - that it's about the "right tool for the right job" - is obvious. But in the wider world of business and IT management, it's also unfortunately true that through a mixture of vendor marketing/advertising, quick-n-dirty reporting and weak industry commentary, an awful lot of people have for some years laboured under the impression that "J2EE is the answer. Now what's the question?" (There's also a lot of conflation of "Java" and "J2EE").This belief is now starting to erode, and that's what is prompting stories like the one in [i]Business Week[/i]. It's over-simplified, of course - but I for one am glad that the questions are now being asked in forums like that.

3 localhost commented Permalink

that is pretty funny. steve mills was regularly riffing about java as an end game about three years ago.and what the shit is wrong legacy - that just means stuff you make money from...

4 localhost commented Permalink

Mike Milinkovich of Eclipse really nailed this issue in a recent blog entry. Thanks to JamesG for the pointer.

Add a Comment Add a Comment