Two conversations over the past few days started a train of thought about where Java is right now, as did the settlement between Microsoft and Sun, the new JCP revision, and the new 1.5 JDK.

One conversation was with the author of a messaging system, talking about the use of his SDK to create a simple grid or service-based system. In short, what we talked about was a lightweight replacement for UDDI, with the conversation points being that it's far easier to manage on many levels, among other things.

Another conversation was with someone who was looking into some Java APIs that he'd previously skimped on. His sense of revelation was amusing on some levels, and gratifying on others.

I think the Java development community is holding its breath, figuratively speaking, waiting for something to happen. We're on the cusp of something, and I'm waiting to see if it's heaven or hell.

It could be either one, after all. Java's been the target of many products and vendors who see its weaknesses - often the result of choices made to create very particular strengths - as something to repair at the cost of its capabilities. Java's ability to run anywhere consistently is a strength, after all, unless you desire spectacular performance in a specific venue - but if that's what you want, and you don't care about the other platforms, then the strength becomes a weakness.

Likewise, we're seeing a lot of fairly new APIs maturing, and people are still figuring out how to use them. In this, the JCP is doing a great job, although I'm still waiting for information on normative use to be propagated. For example, I'm enjoying investigating JMX - which isn't really a new API, having existed since 1998 and finalized in late 2002 - but I have yet to see its critical mass or how people are really using it in the field. JMX isn't unique in this: the list of APIs with similar problems would include Swing, EJB, JNDI, the classloader APIs, the SPI mechanism in Java…a seemingly endless list of core concepts that people are left to fumble along with on their own power, dependent on their willingness to investigate.

I suppose it's a testament to the simplicity and power of Java that people would prefer warping its deployment rather than abandoning the language and concept altogether. That said, it gets tiresome defending the gates against people and companies who should know better. On the other hand, I'm also left wondering about the stewardship of Java. Open source advocates are screaming that it should be open, but they're also the ones who most often abrogate the core strengths of Java; Sun itself has managed to create the situation where stewardship and education are in question.

I can't say I know what's next for Java. I can tell you that every day, despite being fairly jaded, I'm impressed by the number of things you can do well in this environment, and that I find my knowledge is constantly dwarfed by the possibilities. It's frustrating, really - because some day I'd love to have a problem presented to me where all I have to do is solve it, as opposed to having to research how I'm supposed to solve it, and finding a maze of options.

What do you think?