I read the article with the mindset that maybe I am biased and can't see that Java is dying. I was hoping for something that raises flags about things that we (the Java community should be thinking about).
I found a couple of issues with the article. It is in general pessimistic about a whole lot of things, but there is very little if any points made about problems with Java. The point that the article mentions is that Java is 'withering' is correct - which according to their points isn't that they are saying Java is dying. It makes the point the point that there is a lot of code that is getting deprecated and that old Java libraries has been replaced with new. This is great - I have to say that I am happy that this Java infrastructure is evolving even when it old. I noticed the editor seems to be a coworker of the author. Which explains the issues/quality the article. I think the only possibly interesting point that the article made was that there is a growing number of frameworks that are interlocking and increasing fragility. But, ofcourse Maven was not been discussed. Beyond that there were some concerns with Java that were did come up and should perhaps be discussed here: 1) The concern that the article started with, is that really old code does not run anymore. I have experienced this. I would like to It will be great to read more on how big of an impact this is. 2) The other point was one of code reuse. This in my opinion is not a problem when it comes to using external libraries, but I have noticed that code reuse needs to happen more within large application. I am not sure what the answer here is - but perhaps we need better development practices to facilitate these (something akin to code reviews and/or design patterns). Vineet -- Founder, Architexa - www.architexa.com Understand & Document Code In Seconds On Tue, Jan 24, 2012 at 3:14 PM, Josh Berry <[email protected]> wrote: > Finally flipped through the latest issue of IEEE's Computer magazine > and I found the article "The Java Tree Withers." Abstract is simply > "The Java report card: infrastructure gets a D, code reuse gets > an F." > > Was curious to hear thoughts from in here about the article. Right > now, you can find a pdf by just searching on the title. Apologies if > this has already been discussed. (Additional apologies for not being > able to just link to a page with the article...) > > -- > You received this message because you are subscribed to the Google Groups > "The Java Posse" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/javaposse?hl=en. > > -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
