Skip to content

Sad Times In The Land Of Java

I knew it would happen eventually! It’s not unexpected.

Oracle was 100% bound to screw Java over. Bound to. never had a skerrick of doubt.

The first strike (not really Oracle’s fault but it is out there and needed proper management): a spooked community. Java devs are loyal beasties and really wanted some “warm fuzzies” from Oracle. They got squat. All those third-party organisations that based their products or enterprise strategies around the Java platform wanted assurance of a light touch. Did they get it…hah!

Instead, they got…

The second strike: Oracle suing Google. Anyone outside the legal community going to benefit from that, do you think?

The third strike has now arrived: Google backing out of JavaOne. Hear that sound? That’s the thunder of a community running away. Way to go, Oracle!

We all know that three strikes and you’re out…

Where to now?

Time to start polishing my C#?

Haven’t used Objective-C since the NeXT days, but maybe an iPhone betting game would be a winner: “What stupid thing will Oracle do next?” I envisage some neat graphics: an animated Larry sailing around on a ocean of lawyers, occasionally dumping assets overboard…The winner each week would get the major prize: a cup of cold instant coffee; all the other players would have to reboot their devices.

Tags:

C, Java Enterprise Edition, JEE, J2EE, JBoss, Application Server, Glassfish, JavaServer Pages, JSP, Tag Libraries, Servlets, Enterprise Java Beans, EJB, Java Messaging Service JMS, BEA Weblogic, JBoss, Application Servers, Spring Framework, Groovy, Grails, Griffon, GPars, GAnt, Spock, Gradle, Seam, Open Source, Service Oriented Architectures, SOA, Java 2 Standard Edition, J2SE, Eclipse, Intellij, Oracle Service Bus, OSB