Read on for a summary of the final day of JavaOne 2010.
More tales from JavaOne 2010 - Wednesday sessions...
Read on for summaries of the sessions I attended on Day Two of JavaOne 2010.
JavaOne 2010 is over now, and I intend to post a write-up of each session I attended throughout the week. Read on for my impressions of the opening keynote Sunday and the Monday sessions.
I've decided that it's about time I started blogging again, and what better time than JavaOne 2010?
I've fortunate enough to be able to attend this year, courtesy of my employer , and it's shaping up to be an interesting conference. Some interesting questions I hope to get answers to next week:
- Will Oracle sue the entire universe (just like they are doing with Google) over the use (or not) of Java?
- Will Java 7 ever come out?
- If either of #1 or #2 occurs, will the fact that Sun open-sourced Java into OpenJDK save us all?
In all seriousness though, I'm looking forward to hearing what the future of my favorite language/development platform has in store, and I plan to post it all right here, so stay tuned...
There appears to be some hope for Java developers on the Mac platform... it is now possible, thanks to Landon Fuller , to build Java 1.6.0_03 on Mac OS Leopard.
I can confirm that this works, at least for non-GUI code. I successfully compiled and ran a 64-bit VM. 32-bit was more problematic; all attempts at building caused a JVM crash which I was not able to overcome.
Details and benchmarks after the fold.
Recently I have been dealing with the disconnect between Mac OS X and Java 6 , specifically that Java 6 is not available. This is not intended to be yet another diatribe on the evils (or not) of Apple's approach to this. Rather, it has gotten me motivated to work on some tools to make creating cross-platform GUI code in Java a bit easier to manage.
You've seen them. Maybe you like them, maybe not, but Tag clouds are here to stay (at least until someone invents something better). This article details how the tag cloud for this web site was created.
One little-known feature of the Java Servlet Spec allows for encoding session identifiers in URLs. In theory, this allows browsers without support for cookies to maintain session state with your website. In practice, however, there are several problems with this approach...