What Java really needs right now
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?