Dr. Dobb's is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them. Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.


Channels ▼
RSS

JVM Languages

The Future of Java: Part 2


Surveys and Blogs

In April 2006, Sun sent a survey to members of the Java community in order to solicit feedback on the direction Java was going, or should go. The survey asked for areas to be improved or changed for the better. In return, Sun has invested in the community by encouraging its developers to actively blog about the future of Java. At sites such as http://weblogs.java.net, you can read blog entries from the actual people who design and build the Java future. Again, the information flow goes both ways.

You can read from an aggregated view of all Sun-sponsored, Java-related, blogs at http://planetjdk.org. Here, you will find entries from developers of Mustang, NetBeans, and the Glassfish project.

Don't let the future of Java escape you. Become an active part of the community, if you haven't already, by visiting https://mustang.dev.java.net and http://community.java.net/jdk often. Be sure to also sign up for a Sun Developer Network account (http://developers.sun.com), and to become a Java Community Process member.

Sun was actively pushing people to sign up for this network of communities at JavaOne this year. Why? Because it's important to the future of Java to ensure that a healthy community of developers exists. It's also important that the future is guided by individual developers like you, not just corporations or other entities. By helping to guide Java's future, Sun is doing its best to ensure Java's success for years to come, and you're doing your part to ensure that Java will continue to be what you need it to be in the years to come.


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.