Oracle's Comments On JCP EC Nominations

Last week the JCP released the List of Candidates to the JCP Executive Committee. Since then, Oracle has issued a couple of comments and, given the interest in the topic, I'm copying them below.

In a post to the JUG Leaders mailing list, Oracle commented on their choice of Hologic for one of the ratified seats; I'm coping the first paragraph verbatim below; check the full email here.

"There has been quite a lot of discussion over the past week about our JCP EC nomination. We thought we would offer our perspective. We nominated Hologic, as with Credit Suisse earlier, to inject some much needed Java end-user and business perspective into the Executive Committee, as opposed to standards, technologist, technology vendor, and developer community perspectives - all of which are already well represented. Those roles also overlap, as we have well-recognized technologists, like Josh Bloch, who are also representing vendor interests. JCP members may disagree with the need for more end-user perspective on the EC, but we think it's an important view that has been underrepresented to date. Having the perspective of a company whose business depends on Java technology -- not as a technology vendor, but as an informed consumer of Java technology -- is valuable."

Then, in a separate statement, Oracle commented on Doug's absence and Java SE 7 and 8:

"Oracle highly values Doug Lea's contributions to Java and hopes to continue to engage him in the community moving forward. We were disappointed with his decision to not seek another term on the JCP Executive Committee. We believe that the EC is ready to move Java SE 7 and 8 forward, and we will be submitting those specification requests very shortly. With the specification requests for SE 7 and 8 in place, the JCP's normal mechanisms for advancing Java - technical work going on in expert groups, subject to EC approval - will be functioning again. Although we are committed to improving the JCP, we also believe that the JCP is fully capable of supporting vigorous debate and deep involvement and contributions from a variety of individual and corporate participants, and we feel confident that the vast majority of EC members would agree."

Comments:

Having Hologic is really a bad move towards Killing Java.

I'm sure there are more companies that can present end-user better than Hologic.

The only difference is Hologic is pure Oracle stuffed turkey.

Posted by Liyu on October 26, 2010 at 10:25 PM PDT #

With this new Oracle stunts. Java as open platform is no longer desired. Java future will be full with lawsuits, expensive licences and bleak.

OpenJDK future is seriously in doubt. In later years Oracle may ceased the support for OpenJDK, or starts suing another company whose adopt openJDK classpath.

I deeply regret for building my programming skills around Java. As I see more organizations(ex Apple, governments) drop Java as their platforms. From desktop to the server- side, people are afraid to use Java.

Before I was a proud with my Java programming skills(Glassfish, servlets, JSFs, Swings and etc2) and I maybe even the first programmer who uses and understand JSF in my country. sigh...

Now its now all gone. Maybe I should reboot with .NET or Python afterall.

Posted by javaprogrammers on October 27, 2010 at 05:14 PM PDT #

OpenJDK is very solid. With IBM joining, it will be even more so. And we will see what will happen on the Apple side.

Hang in there; I believe things will look better in a few weeks.

Posted by Eduardo Pelegri-Llopart on October 28, 2010 at 01:33 AM PDT #

> javaprogrammers
Java is growing.
Look at the sheer volume of Java projects by the Apache Foundation vs C# projects by the same Foundation. Tomcat, Ant, Maven, James... 4 new committers on Harmony.
Look at the growth of Berkeley Java DB HA.
Look at Android!
Man it's an exciting time to be a Java developer!

Posted by Uhnonymuss. on November 03, 2010 at 09:57 PM PDT #

Post a Comment:
Comments are closed for this entry.