How the Java Community Process Has Changed and Where It's Headed

DZone 's Guide to

How the Java Community Process Has Changed and Where It's Headed

Perspectives on the Java Community Process, and its future, are depressed.

· Java Zone ·
Free Resource

To gather insights on the state of the Java ecosystem today for DZone's Java Ecosystem research guide to be published in September, we spoke with 15 executives who are familiar with the Java ecosystem.

Here’s who we talked to:

Joel Depernet, E.V.P. Global Research and Development, Axway | Sacha Labourey, CEO and Founder, CloudBees | Rick Reich, CEO, Development Heroes | Asad Ali, Principal Software Developer and Lisa Hamaker, Marketing Manager, Dynatrace |  David Park, V.P. of Products, HackerRank |  Charles Kendrick, Founder and CTO, Isomorphic Software | Wayne Citrin, CTO, JNBridge | Raymond Augé, Senior Software Architect, Liferay | Laura Kassovic, Founder, MbientLab | Cameron Wilby, Co-Founder, Origin Code Academy | James Faulkner, Technology Evangelist, Red Hat | Paul Trowe, CEO, Replay Games  | Calvin French-Owen, CTO and Co-Founder, Segment

We asked our respondents, "How has the Java Commuity Process (JCP) changed ove the past 10 years and what do you see changing in the future?" Here's what they told us:

  • JCP changes have been tough given the situation with Oracle. Oracle wants to benefit from Java like a pension. It will not let others have too much freedom with the product, yet they have their minds on other things. I hope .Net puts pressure on the Java Ecosystem since Oracle’s control is very tight. There are a lot of politics and I don’t see Oracle opening Java like Open Source. They like to be in control.
  • When Oracle purchased Sun there was a culture shift from people passionate about programming. Increase in the delivery of JavaScript. We’ve changed from the server side to the client side. This has kept Java relevant. There’s an underlying perception that Java 8 and 9 will lead to a more closed ecosystem. There’s greater fear of vendor lock-in driven by what’s going on with the cloud platforms.
  • The Java Community Process is slow. Modules have been put off for a long time. JMS (message service) was stuck at 1.1 for a long time and launched 2.0 in the past year. Speed is a problem. I hope things speed up and get simpler – it’s very complicated. Things being defined is rather complicated. .Net is easier to use because Microsoft is in charge.
  • I see the Java Community Process becoming nonexistent and stagnant. The only motion is from the external stewards. The future for the JCP, consistent with the history of Java where most work comes from the non-Oracle stewards (Apache Software Foundation, Eclipse Foundation, and the OSGi Alliance). It’s becoming more difficult; however, the Java community is strong and will keep the language viable. Oracle should open up and let others contribute.
  • With regards to the JCP, Oracle has put a price on the JVM to generate revenue. We discussed moving to the open JDK to save on fees. I don’t have a feel for where the JCP is going in the future though we are keeping a close eye on it. I have no expectations; therefore, I won't be disappointed.
  • The JCP hasn’t changed much. The goals are still valid. We believe in standards and interoperability. The people active in the community have been driving the changes. In the future, I see the JCP promoting other standardization efforts. A seen with the rise of GitHub, grassroots standards are more effective.

How has the JCP changed from your perspective and where do you see it going in the future?

java ecosystem ,java community process ,jcp ,jms ,osgi alliance

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}