Skip to main content

Can Java as we know survive in Oracles eco system?

Posted by malcolmdavis on November 2, 2010 at 9:20 PM PDT

Many people were concerned when Oracle acquired Java.

The concern seems warranted in light of lawsuits, Gosling & Lea leaving important positions, Apple dropping support, the death of JCP, and Oracle no longer providing TCK for Apache going forward.

Unlike IBM, Sun, and others, I have never used any open source of free products produced by Oracle.  (I've tested numerous Oracle products like JDeveloper, but everything I touched fell way short of expectations)

The conflict steams from the core of Oracle existences.

Oracle makes their money from selling the corporate manager, not a software developer that actually has to write code every day.

It is apparent with recent revelations that Oracle's corporate approach in impacting Java, and is the mindset is having a negative impact on Java.

During the War Between the States, generals applied old style Napoleonic war techniques with modern weapons.  The results of applying the Napoleonic system were disastrous. 

Oracle shouldn't think that the same internal processes that made RDBMS a success can simply be applied to Java.   

For Java to continue thrive and grow, Oracle needs for realize the impact, develop an internal eco system separate than the present approach, and fix some burnt bridges. 

Gosling thinks Java has too much momentum for Oracle to do real harm.  Give Oracle a chance, Gosling may be surprised how much damage Oracle can cause Java.

Related Topics >>


Can Java as we know survive

I too fear for Java's future.

In the old days, there were lots of technologies that everyone though they would last forever and they are now gone.
Clipper used to be THE language to develop database applications in the MS-DOS system, and I still remember the days when Turbo Pascal/Delphi were very important.
Bad management can kill the use of a language, lets hope that Oracle does not kill Java as we know it.