Skip to main content

What Java really needs right now

Posted by calvinaustin on August 25, 2010 at 12:42 PM PDT

The recent complaint from Oracle to Google is probably one of the most key events that may dictate Java's legacy. Is this what Java really needs or are we missing something else?

Lawsuits are incredibly exciting for legal teams, albeit lots of work. For the rest of the company on either side the novelty soon wears off, cases can span multiple product releases and even years so its a constant that affects both sides.

However that wasn't the first thing that comes to my mind when I think of Java. Yes project coin for Java 7 is interesting, I possibly could dabble in a lamda one day, I've still no idea if or when we will even see Java 7.

Part of my teams responsibility is maintain our network infrastructure too. If you haven't used cisco equipment in a while, most devices can be accessed via a browser and yeah its a Java applet. Oh but that doesn't work on most of our firefox browsers due to a known issue and our options are to reinstall a key piece of our network hardware or find an old browser (with a plugin that works), although we know we should reinstall, we either go with the old browser or the old command line cisco interface.

Just yesterday our sales guy was trying to use some collaboration tool with a customer, he had IE and yeah the tool used Java, oh, he came round, apparently it wasn't working, could I look into it. I had to tell him if it didn't work for him there isn't much chance our customer would get it working with IE either.

Just one day it would be nice if I clicked on my linux firefox upgrade and when it says find java plugin it doesn't say manual install. Even with the Java 6 update client fixes it seems only a band-aid to a long time sore.

Maybe google and oracle can settle up nicely, who knows but is it what Java really needs right now for the rest of us?

Related Topics >>


Support things that work, ditch things that don't

Java applets? Was this ever a good idea? Flash, albeit popular, was not a good idea either. What we need is for developers and managers to stop supporting technology that does not work. I hope that whomever is responsible for the decision to use a Java applet to develop a web application at Cisco is no longer making technical decisions.

That's cool

Great blog, I looked all over google and found u. Regards Mahjong

Well said

I wish Google would have bought Java instead of Oracle. There is nothing worse than seeing such a great platform getting destroyed in slow motion. Oracle should clean up its act or get out of the way.

That's a really interesting

That's a really interesting question. If I had to choose between fixing the depressing Java plug-in mess or Project Lambda, and could only choose one, I would come down on the side of a plug-in whose installation/update works as well as Flash.

Right now, on my Windows 7 machine,  a Java icon appears ever so often in the tray. Whenever I click on it, I am asked to authenticate the admin account (fair enough), then I get an error message about a failed download, and the icon goes away. On Linux...don't get me going.

project lambda

Cay I'm with you although I'm not sure if it came through clearly in my original post but I think project lambda is all fine, and given the few working on it, its cheap, however the focus that ultimately could have been spent on repairing the experience for java users will now be diverted to the lawsuit.

I think Sun Tzu put it nicely.

Thus it is that in war the victorious strategist only seeks battle after the victory has been won, whereas he who is destined to defeat first fights and afterwards looks for victory.

It seems like the victory that could be in reach is royalty fees and damages for patents. That isn't the war that needs to be won...