; Date: Tue Oct 21 2008
What does this mean?
It means that client side Java has been getting some long long long needed attention and improvement. There were years when, obviously, the attention was on server side Java and, obviously, client side Java suffered. It is a relief to have attention on client side issues because in truth Java was the first RIA platform (long before this term was invented by a different company) but it was hampered in playing a significant role in RIA by, uh, shortcomings in the client side (sigh). 6u10 fixes a lot of issues and enables the underlying graphics changes needed for JavaFX.
But what does this mean for the OpenJDK project? As was pointed out in an
openjdk.java.net mailing list a couple days ago, 6u10 represents a proprietary fork of code we're working on opening. Um, well, okay, uh, that's certainly true from one point of view. As good as the new features in 6u10 are it is a split between the JDK and OpenJDK, and unfortunately it's still unknown if/when we'll be able to move that code into open source. There was a sequence of great conversation in
September on the email@example.com list in which we made it clear that no decision has been made about if/when/where/how the new stuff in 6u10 would be made open source. Please stay tuned and maybe we'll have good open news relatively soon.