I just discovered that every email that passes through procmail is logged (I’d forgotten I’d set it up like that). A quick analysis of the log shows that 62.8% (5473 out of 8655 emails) of my email is moved to the spam folder by procmail (after being identified by spamassassin). There are a few extras that wind up in my inbox but no more than one or two emails a week and I’ve only come across about 5 false positives since I set up spamassassin (most of which are QANTAS’s flight detail emails). That’s a pretty sad state of affairs really. Fortunately, thanks to spamassassin, I use my email completely unhindered.

So apparently I’m off to Java One. The details are all very sketchy at the moment but apparently the flights involved will be something like: Depart Brisbane on Friday 26th June, to Auckland, then Los Angeles (I think) then “SFO” (can you tell I have no idea about where I’m going yet?). Should arrive at the final destination on Friday 26th June (apparently just before I left). Stay somewhere, do something of which the only certainty is going to the Moscone centre while the conference is on, probably get arrested trying to sneak into WWDC which is also on at the Moscone centre and watching the 4th of July fireworks from somewhere. Fly out on the 6th of July via Sydney (skip the New Zealand connection this time) and arrive back in Brisbane on the 8th of July. So yeah, pretty disorganized…. Any advice/pointers/suggestions/opportunities to meet up would be welcomed. More details as they unfold and I’ll do my best to blog as much as I can while I’m there, this is probably as good a place as any to store my notes.

Rich Bowen talks about his camping trip and it reminded me of something my Father and I used to do a fair bit of – spider spotting. In Australia we have a huge range of different spiders and they are literally everywhere – much more common than most people would be comfortable with. Most of these spiders are really small so you don’t see them in the light of day but during the night spiders are much easier to spot because of their brilliant blue eye-shine. Spider spotting basically involves getting one of those “pencil” torches (2 AA batteries and you twist the end to turn them on/off and adjust how focussed the light is). Turn it on and adjust it so it has a single focussed beam, then hold it just below one eye and look straight down along the beam of light. When you see a spider its eyes will shine back a bright turquoise color. You’ll find them everywhere in the Australian bush, around the ground, on tree trunks, in trees – pretty much everywhere you look there’ll be a bright blue set of eyes looking back at you. Just don’t do it if you’re afraid of spiders or you may never feel safe again. One other thing, Rich writes:

Every time I see someone talking about the wonders of GPG I think to myself, “I should probably at least have a GPG key” and then I promptly forget about the whole deal. When Bertrand mentioned he was getting into it I went through the same thought process but this time, because of the exceptionally convenient link to an exceptionally conveniently packaged OS X version of GPG, I actually got around to doing something about it.

Joshua Marinacci has started writing a new XHTML renderer in Java. He’s done a pretty impressive job at getting started but I get the impression that he has no idea what he’s in for. At the moment the rendering is pretty good but the speed is absolutely awful. While you shouldn’t ever optimize too early, it’s certainly possible to optimize too late and HTML rendering is one of those areas where you suffer death by a thousand cuts. I wouldn’t be at all surprised if he has to rework large parts of his architecture to reduce the number of string comparisons to speed things up. That’s the kind of thing that you probably should think about before hand (note that I haven’t even looked at the code so he may have already considered that). The other thing that I notice is that it doesn’t seem to support incremental layout yet so it has to wait for all the images to download before it can do anything. In an HTML editor that pretty easy to do because you’ve already got the code to update the layout quickly in response to changes but I’m not sure if there’s an easy and efficient way to do it without having to implement all that. The big complaint I have though is that there doesn’t seem to be any licensing information which is something you really should sort out at the very start of the project so people know what they’re getting themselves in for. Anyway, it will be interesting to see how the project goes. Update: The project page says the license is LGPL. Oh well, guess I won’t be having anything to do with it then.

Java.Net is having conversations about removing stuff from the standard Java libraries because they’re getting too big. The comment below really stuck out at me:

Combine that with a program to remove redundant functionality (by declaring it deprecated so it gets killed 2 releases later) and you have a powerful tool to get people to stop using old stuff like Vector and StringTokenizer.” Vector and StringTokenizer aren’t “old stuff” – they’re extremely useful classes with a specific purpose. Vector is a guaranteed thread safe implementation of List – something you can’t possibly get other than declaring that you want a Vector. To clarify that, consider the method signature public void doStuff(List items) what are the thread safe requirements on items? There’s no way to know and the default assumption would be that it doesn’t have to be thread-safe. Whereas with: public void doStuff(Vector items) the code may be less flexible now but the compiler now guarantees that you’ll get something that at least claims to be thread safe. It is still possible to extend Vector and perform non-thread safe operations but that would be a bug in the extending class because it failed to live up to the contract of the parent class. StringTokenizer is a particularly useful class in that it provides the simplest way to break a String down into tokens. You could iterator of the characters yourself or you could use regex to do this but manually iterating is reinventing the wheel and regex are highly inefficient for doing what StringTokenizer does. Furthermore, nothing in StringTokenizer is marked as deprecated in my copy of the Java 1.4 API, nor anything in Vector. Seriously, just because you don’t find something useful doesn’t mean it’s not useful.

While browsing a collection of stupid pranks (most of which aren’t at all funny) I stumbled across some really great responses to a “10 year old school kid” (who in fact was the prankster) writing in to ask all 100 US senators what their favorite joke was as part of a school project. I think it’s fantastic to see that a number of them replied, but one that really stood out was this one from Senator Jon Corzine from New Jersey. Not only did he take the time to respond with his favorite joke, it was actually a good joke and he took the opportunity to teach this young child about the state of New Jersey. Now whether or not he wrote the letter personally or one of his aids wrote it for him, it’s still great to see that there’s a culture in that office of going beyond the minimum required and taking the opportunities to do good that are presented. Disclaimer: I know nothing else about Senator Jon Corzine, I’ve never been to New Jersey (or the US for that matter) and until I read his letter I knew nothing about the state of New Jersey (which for some reason that noone seems to know, is called the Garden State). For the record, “the garden state” in Australia is Victoria. Who knows why…. They have since changed their license plates to read “Victoria – On the move” to which most Queenslanders add: “to Queensland”.

You are a unique and beautiful snowflake – just like everyone else.

This is either a joke or the most biased reporting I’ve ever come across. If it’s a joke it’s not funny and if it’s biased reporting it’s so overly biased as to be obvious and thus much less effective. Not that I don’t think Blair’s labour party deserve to be voted out but comparing them to Hilter’s Nazi party is way over the top. For the record, the article appeared on the front page of Google News.

Firmly in the “what were they thinking?” category: two menu were arrested and charged with animal cruelty. What did they do? Kill a live mouse (each) by chewing it. The management of the Exchange Hotel where the incident occurred as part of an organized promotion claim “they knew nothing about it”. I’m the sure the expense claim for a holiday weekend on the Gold Coast (which was to be the prize) wouldn’t require any explanation….

David Starkoff points out this case regarding the provision of adult entertainment on Good Friday. David points out how “ironic (apt, perhaps?)” it is that the Common Prayer Book is pivotal in the final decision. However interesting it may be that:

the Almanac annexed to the Common Prayer Book has been regarded as part of the common law, and in consequence would have been received into Australia as part of the common law (Halsbury, 3rd Edition Vol 15 para 611 and Vol 37 para 133) from my exclusively non-lawyer stand point I would have to pick the following excerpt as the highlight of the document:

Apple has a bug tracking tool called radar and they let any ADC member log bugs into it which they may or may not get around to fixing. They don’t however let anyone outside of Apple view the current bugs in the system. This causes great amounts of flamage on Apple’s java-dev list (and I imagine many of Apple’s other lists as well) about whether or not the list should be open. Every few weeks someone just has to come along and ask how they search the open issues and it starts again. Last time it came up some actual progress was made on the issue. Someone suggested creating a publicly accessible, unofficial bug listing that people could log bugs in, in addition to logging them with Apple, and those bugs would be publicly accessible so that people could find any work arounds that might be available. Of course there are three draw backs to this: 1. People may log the bug just with Apple and not in the 3rd party bug reporter. 2. People may log the bug in the 3rd party reporter and not with Apple. 3. People may see that the bug is already logged in the 3rd party bug reporter and not log it with Apple. Problem 1 is a non-issue. It just means that that particular bug report isn’t publicly available. Too bad, so sad. Problem 2 is a major issue because it means that Apple will never know about the bug and thus never fix it. (Nothing gets done at Apple without a radar issue being created according to the Engineers who’ve commented on the matter) Problem 3 is also a major issue because Apple prioritizes bugs based on how many duplicate reports they get. If people see the bug has already been reported they won’t report it again and Apple will think it’s not important and fix it whenever they get around to it. Obviously the combination of problems 2 and 3 is particularly disastrous. So the question then becomes, how do you create a system that lets people easily log bugs and search for existing bugs while still getting most people to log the bug with Apple? The ideal solution would be to have any bug logged in the public system automatically logged in Apple’s system as well. Existing bugs could have a button that allowed users to log a duplicate bug complete with a reference to the original issue with one click. The trouble with that approach obviously is that it requires access to Apple’s system which I don’t have. I’m not sure they’d appreciate having an automated system screen scraping their bug reporter to log bugs. It also doesn’t encourage people to specifically log their own case and thus can deprive the Apple engineers of that one subtle bit of information that suddenly makes the bug simple to reproduce. It’s probably possible to make the form look just like Apple’s so that it’s a simple matter of copy and paste to log the bug in both systems. A big red notice about how Apple wants to get duplicate bug reports might help alleviate problem 3 but it definitely wouldn’t solve it. All up, I’m just not sure if a publicly available, 3rd party bug database would help or hinder the situation. It would definitely be useful to have a place to go to search for existing work arounds though.