As a much debated topic over the last half-decade or so, it has to be clear now that Java is beginning to lose it’s grip on the application programming world.   Surely anytime something is discussed so often and so passionately, we must conclude that there is some validity to the both sides of the argument. In this case, it’s beginning to look like Java is losing the argument.

I have long since seen the writing on the wall for Java even though it is still the leading platform and language for building robust and scalable web applications, embedded software, etc.    Java has a footprint in almost every arena of software. The problem is that it has become simply outdated. It was not built to do what we’re trying to do today.

Now, the “javanistas”, gurus, ninjas and architects are probably going to vehemently disagree; but that’s ok and understandable.   To say that Java is still viable and will be around for a very long time would be a huge understatement.  When you look at what’s going on in the industry, however you almost have to notice the shifts in technology, where things are headed and the fact that Java does not factor-in as heavily as it used to.  Nowadays, when I think about building a new application or website, I first think Grails or (lord help me) PHP or I think to leverage some CMS/platform like Joomla, Wordpress or Drupal.  Beginning a new site in Spring MVC / Hibernate or Struts2 / Spring / Hibernate flat out gives me a headache.  Again, I’m going to get killed there, but oh well.  I’m certainly not the only Java developer that feels this way.  I’ve made a (good) living off of Java, but it can be a bear sometimes and many times when things simply shouldn’t be difficult.

The bottom line is that time, politics and business (see Google exec worries over ‘rudderless’ Java) are wearing on the old man.  Java’s not quite the new COBOL, but all you young Java gurus might want to take your blinders off that’s all I’m saying.