I was talking with some colleagues the other day, and between discussing the technical issues we were meeting about we also talked about activities we do in our "spare time". One of them described these activities as "garbage collection". Wow, what a concept.
Here's a few thoughts on harmonizing (or garbage collecting) ones life I've gleaned from 13 years studying various spiritual practices....
Rather than bitching about problems this time I want to take the opportunity to congratulate Sun for the JDK community project and the progress they made. Now I can see the light at the end of the tunnel where Java could become an open-source project.
If you haven't filed your regression in the contest, you're almost out of time. See here.
I came across this article Former Sun Exec Calls for Firm to Open-Source Java which is repeating yet another in the series of calls for Sun to open source our Java implementation. The article itself is examining a blog posting by Peter Yared, An Open Letter to Jonathan Schwartz. I absolutely cannot comment on the call for open sourcing Sun's Java implementation, so I won't. However there is a...
The JSRs that define the JMX API are being updated through the Java Community Process.
There was an interesting discussion thread on javalobby last week: Poll: Delay Mustang in favor of more fixes? ... I think the discussion added a lot of value to the discussion around Java and especially the in-progress Mustang release.
I wanted to focus on one statement that really stands out to me as the project leader for the Mustang Regression contest: "Sun appears commited to fixing any/all regressions prior to release". That's exactly the idea we wanted to reinforce with the public.
Just a quick note - the Mustang Regression Challenge is winding down. The deadline for entry is March 31, 2006 at midnight. So far we have received 44 entries, some of which have already resulted in fixes being made. The more regressions you find, the more issues we will have fixed before Mustang is finalized, and the better Mustang will be in the end. Well, that's the theory anyway.
Luis-Miguel Alventosa from Sun's JMX Technology team will be presenting Monitoring and Management in Java SE 5.0 at Java Expo '06 in Madrid, on Tuesday the 21st of March.
Yesterday Ray Gan blogged about the JDK
Community listing some of the facts about the Peabody
project. If you never heard about that project then you are not alone
and I only now about it because Joshua Marinacci gave a presentation
about it at the LA-JUG last year. But even without knowing about the
Peabody project is became a JDK contributor last year in November and
started to code a fix for bug #6212146
which I has sent to Sun for a review by the end of November. I got an
initial confirmation that the bug fix was received but that was all I
heard from Sun for a long time. Then January 2006 Ray blogged about the
of JDK Community and I responded complaining about that I got
no feedback from Sun about my patch. A little bit later I finally got
an email from Michael McMahon (1/31) that they started to look into the
patch. I also spoke with Matt Ingenthron from Sun about it and he tried
to find out what is going on and to bring some more transparency into
the JDB Community. Needless to say that I did not get any feedback
Sun started the JDK Community on java.net about a year ago. I'd like to provide an update to where we stand now (I've got numbers) and where we're going. We also want to hear from you too.
This is the third blog in a series on architecting applications. In
the first blog I discussed the application I'm going to develop,
how it would be architected, and briefly went over the model. In the
second article I motivated the need for an Application class that is
suitable for typical Swing based Apps, as well as the functionality it
should provide. In this third installment I'll go over the role of the
controller as used in the MVC architecture. As promised, this blog has
a runnable demo.
I'm listening to JavaPosse #37 which is part 2 of their interview with Bruce Eckel. The interview is highly interesting and I highly recommend it. This is my first exposure to this guy, and it's clear he knows his stuff and is very articulate. Must be why his books are popular.
There's a thread in what he's saying that I want to respond to. Namely that a Good Language is one which makes it...
The other day I made a blog posting concerning Bendy classes and dynamic programming, discussing a meme I'm seeing in developer blogging. That idea is there are various dynamic or scripting oriented languages which make it easy to write quick programs with loose binding (there are probably other benefits to those languages). Supposedly Java is a dinosaur with its rigid binding, compile time...
Mustang, a.k.a. Java SE 6, is getting ready to bolt out of its corral. We've done a lot of good things in Mustang. There's a recent article published on devx.com giving an overview of changes in Mustang, plus we've published the official docs which you can browse.
There's one new feature that I want to talk about today, and that's the support for scripting languages in Java. I have some...
Jack Herrington has published this article: Going dynamic with PHP claiming to show some things PHP can do which Java can't.
Okaaaay... This is another of the articles in the meme that dynamic languages are great, and rigid languages are uncomfortable. I don't know if I got the analogy right this time, let me know please?
The problem he poses is about implementing the database interface classes. The traditional method might be to write one class per database table, expose get/set methods for each field, etc. You'd end up with a tedious implementation and a lot of typing of highly similar code. He poses three possible solutions, and claims that PHP implements the best of the three.
One problem with the article is there's more than three possible solutions. The problem with the proposed solution is it doesn't give early warning of broken code, leading to greater expense to fix coding problems.
Whever a writer presents a problem .. and then presents a selected list of solutions .. the writer (maybe unknowingly) is trying to limit the readers thinking to the given solution set. But what if there are other solutions the author doesn't present?
Three weeks ago I launched the Mustang Regression Contest. The grand prizes are five Ultra 20 workstations, which are to be awarded for the "best" regressions submitted during the contest. The other day Ray Gans and I brought them from the a storeroom in the Menlo Park campus to one in the Santa Clara campus. So while moving them I thought to post a picture to show you guys what you're competing for.
These Are Some of my Favorite [Mustang] Things is a listing by Chet Haase of improvements in Swing, Java2D and AWT. Makes for a good read.
Weiqi Gao has a blog posting with early impressions on Mustang, a.k.a. Java SE 6. In all it's very positive talking about several applications he tried which worked fine.
He talks a little about the adoption rate for Java 1.5 (a.k.a. Tiger), and says "I have a feeling that the lack of a 5.1 version has really hurt the adoption of JDK 5".
I want to mention that, what would have been "5.1" are...
Don't you just love carnivals? With the release of JDK 6.0 Beta a new carnival came to town. The day after the release JDK engineers let loose a JDK Blog Carnival and just like the carnivals of old it is chuck full of intriguing information.
I think these should make for a nice extension to the existing Java 5
From an Annotation, one should be able to navigate back to the programming element that it annotates.
For example, a method annotation clearly marked with a Target
of ElementType.METHOD cannot say getAnnotatedElement().getName(),
There are two problems here. The first is the lack of the