With this post, I'm starting a short series of thoughts about what I hope Oracle will do for a set of popular Java APIs, that haven't been dealt in detail in their strategic keynote. Today I start with SwingX.
The first Oracle J1 has just opened its CFP, deadline March 14.
Yesterday I made my proposal submissions for Jazoon 2010 - as usual at the last minute, as now the call for paper is closed. Young speakers (under 26) wishing to make their first experience should recall they have got still time until April 4.
Erasure is a part of the way Java 5 implements generics, so the bytecode loses all the information about the generified types, only generating the proper type casts where appropriated. It's the thing that you scream against when you try to write code such as:
Kenai is being closed, so I'm moving all my projects to Google Code for the Mercurial source repositories and Google Groups for the mailing lists.
I love owls; they are so elegant and have a strong personality (too bad in so many years I've been unable to take photos at any of them!).
As Terrence just pointed out, UE has cleared the Sun/Oracle deal. And I just read this on the Oracle website:
In many previous code examples in this blog I've used the “Finder pattern”, that I've elected as one of my best practices (it's standard in all my new APIs and will be retrofitted to the old ones). Before moving on with more examples, I think it's high time I shortly introduced it formally.
Tree-like structures are a very common pattern. Just to count instances of this pattern in my FLOSS projects:
My first speech of the year will be at the JavaDay 2010 in Rome - officially a JUG event, practically a mini-conference (with more than one thousand attendees). It's free, so save the date.