For those in the “Java™ will never cease to flourish” camp, recall some of the scoffing you experienced back in the early period of Java™’s adoption, the jeers from the C++, C, and maybe even COBOL camp, depending upon the nature of the shop you were in. Now, take those scoffs and perform a search-and-replace: s/Java™/{Ruby,Rails,Python,etc.}/ && s/{C,C++,COBOL}/Java™/. Listen to yourself when you respond to topics like Ruby on Rails. The resemblance is unsettling, don’t you think? Why must everything new (or non-Java, really; newness isn’t even a condition most of the time) be rejected out-of-hand as inferior and “a fad”? The unwillingness to acknowledge (much less embrace) the strengths of alternatives to Java™ ironically serve to undermine your puerile assertion that Java™ is the be-all, end-all in programming.
Read the entire post: http://www.yepthatsme.com/2007/09/18/java-and-the-prodigal-son-syndrome/