The Java Community Process - Is Sun Listening?

cgu queries: "For those who are familiar with it, log4j is one of the most widely used Java libraries today. Sun Microsystems intends to ship an obviously inferior package with JDK 1.4. Is the Java Community Process just a fig leaf allowing Sun to ignore existing development efforts? What has been the experience of other Java developers with the JCP?" There's a bit of history here, so you'll probably want to check out the log4j pages linked to, above. This is a large concern for any language which has developed a community around it, who hopes to assist in its further development. So is Sun paying attention to the community that has rallied around Java or is the Java Community Process just paying lipservice to the intended ideal?

Comments

This doesn't matter.

[topham]

You can fool all of the people some of the time, and some of the people all the time, but you can't fool all of the people all of the time.

Now, just replace fool with please and your done.

This is comparable to choosing to implement something other than Electric Fence in C; the impact on the entire community is negligable. If I choose to use a different logger it will not seriously impact anyone outside of the development group. It may mean the default is less than optimal, and people will use it without knowing there is an alternative which is better, but these are the same people who wouldn't know such a library existed now anyway.