Obligatory JavaOne post

The first two days of JavaOne have been precisely as expected. Big, silly, lots of hype. But there's been some good stuff as well. The big hype efforts this year seem to be around JavaFX and Glassfish. I don't care about JavaFX at all, and as far as I can tell, nobody really does. But my sample is surely biased. Glassfish looks like a good direction, but we've all seen Spring and OSGI, so I think it's a fairly obvious direction at this point. There's also lots of hype about the JVM running on all kinds of devices, but so what?

The modularization stuff is more interesting (JSR 277), and since I never really made time to look at it, this is a nice chance to take a look. The JVM has needed something like this for a very long time, as I know from some unfortunate personal experience. It's a little unfortunate that the solution is yet another layer (e.g., we've still got classes, packages, jars, etc., and now we can add, what, jams?), but there was probably no other way. I particularly like the fact that the spec is designed around an API, making module repositories pluggable.

Anyway, the real story this year actually seems to be a deep acceptance that Java is not the only game on the JVM, and that this is fine. I'm pleased if not surprised at the number of sessions on JRuby, Groovy, Scala, and so on. It's been clear for awhile that Sun has been going in this direction, and it's nice to see it reflected here.

Now I'm catching up at Maxfield's coffee shop, which is indeed a nice place to catch up. (Thanks to Chung-Chieh Shan for that.) But it's starting to get crowded, so it's time for me to get out of here...