Channels ▼
RSS

JVM Languages

The Future of Java: Part 2


Eric Bruno is a Java consultant, author of Java Messaging, and Java blogger for Dr. Dobb's. He can be contacted at eric@ericbruno.com.


In this installment of the "Future of Java" series, I look at the Java community of developers, and Sun's very first move towards open source Java. I recently spoke with Ray Gans, a program manager for Java SE at Sun Microsystems, regarding Sun's role in the Java community environment starting with Java SE 6 (Mustang). What began as Project Peabody, where Java SE developers posted their code weekly for the world to download and see, is arguably one of the first steps Sun has taken towards open-sourcing Java.

Project Peabody is now known as the JDK (or simply Java) Community. Moving towards a participant model for future Java development has given Sun deep insight into both the open source world, and the world of Java developers. Listening to developer feedback provides benefits to both Sun, and the developers who provide that feedback, and in turn has led to a major culture change within Sun. Let's explore this change in more detail.

In November of 2004, Sun decided to give developers access to the source code for early builds of Mustang (Java SE 6) on https://mustang.dev.java.net. People were encouraged to download the code, look at it, and provide feedback. Binaries were made available under a special click-through evaluation license, and the complete source code was available through the Java research license. A lot of excitement was generated right from the start, with over 10,000 downloads of the code drops per month.

Information is a Two-way Street

In March 2005, the program was expanded, and a number of projects were opened up to the JDK community through http://java.net. People had a place to discuss the code, create prototype and research projects online, provide general code enhancements, and contribute bug fixes. If you were at JavaOne this year, you might remember that special recognition and a Duke's Choice award was given to Brian Harry for his outstanding contribution to the Java SE project (114 bug fixes).

If you Sun management why they have put so much time, energy, and resources into opening the Java SE source code to the community, the answer is simple: to provide an environment for information to go both ways (both to and from developers). The goal was to remove barriers with, namely, developers, and to show that Java was built on a good source code base. Even for those not interested in the source code, the availability of early binaries and a site where feedback was welcomed has provided an avenue for people to give their opinion on Java's direction and future.

All of this work has proven to be helpful to both Sun and developers. A dialog between the parties has been opened, and the potential for "surprises" regarding the future of Java has been reduced, if not completely removed. This is further proven by Sun's encouragement and funding of its internal resources (those working on Java) to actively blog about Java SE 6 and 7 (Mustang and Dolphin, respectively).


Related Reading


More Insights






Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Dr. Dobb's encourages readers to engage in spirited, healthy debate, including taking us to task. However, Dr. Dobb's moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing or spam. Dr. Dobb's further reserves the right to disable the profile of any commenter participating in said activities.

 
Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
 

Video