There’s been a lot of discussion about Microsoft’s shiny new patent on putting multiple scripts into one XML file – all of it saying how ridiculous the patent is. This however, gets my vote as best retort. My view: it’s crap, but most patents are. Time to make people go back to having competition I say.

Gregor J. Rothfuss asks:

what will be deployed 100% first, IPv6, the metric system or Unicode? My answer: the metric system, it’s got a massive head start. They all require America to pull it’s head out of the sand and play nice with the rest of the world though so probably none of them will ever happen. Sigh. On the subject of Unicode – what is with defining a universal character encoding that has so many different forms??? UTF-8, UTF-16, UTF-16BE, UTF-16LE, UTF-BE unmarked, UTF16-LE unmarked, collapsed accents, expanded accents. Gah!

Well, I thought I’d download Firefox and try it out for a while (this entry is being written using it). The first thing I notice is it doesn’t look right. Read on if you don’t mind hearing criticisms of Firefox.

Dave Hyatt finally got around to posting to his weblog about the release of Safari 1.2. Some really good stuff has gone into it and congratulations are in order for all involved. Sadly, my most anticipated feature, LiveConnect, appears to be broken. I’ve seen it work when going from JavaScript to Java, but never managed to get JSObject working to communicate from Java to JavaScript. Dave’s blog is actually the first place that I’ve ever seen that actually mentions going both ways, or at least that what I assume he means by:

At last, a simple to use playwright tool! Not at all documented admittedly and looking very incomplete but it seems to work okay. Plywood is a python script that works with latex to format a simple text file and turn it into a PDF laid out according to the Samuel French style. It’s horribly incomplete but it’s a great idea and it seems to work. It also includes emacs bindings to make it even easier, but I’m using SubEthaEdit for now and I already know vi so learning emacs seems like to much work now. An example script would be something like: title: Example Script author: Adrian Sutton characters: Adrian Sutton (AJ) – A very excited new user of plywood. newact: setting: AJ’s office. AJ – [jumping up from his computer] Woooooooo! I found a playwright tool that’s not ridiculously complex. (AJ jumps up and down in excitement then runs off to find a beer to celebrate.) The actual package contains an example that’s even worse than that….

Michael Santos explores a few features of Java 1.5. As part of it he uses the new static import feature and asks what people think of it. I think it’s the most evil invention in coding I’ve seen since while (++i < 5) type statements. If you saw the line of code: long time = nanoTime(); where is the nanoTime() function? In 1.4 and below it is obviously in the current class – in 1.5 it could be anywhere and the only way to find out is to scroll all the way back up to the top of the file and read through every import statement. Then consider something like: err.println("Hello world."); Where’s the print statement? Everyone knows about System.err.println so that must be it, unless err was a debug statement declared at the top of the file… Is it really that difficult to type System.nanoTime() instead of just nanoTime()? Programmers seriously need to learn some more discipline instead of always taking the easy way out and forgetting about the guy who has to read the code after them. In about 3 years time when I actually get to use Java 1.5’s features (backwards compatibility being as important as it is), the first thing that will be added to my coding guidelines will be no static imports – right next to no ++i or i++ embedded in other statements.

Fear stuck deep into my heart, a chill ran down my spine… I reread more carefully what I feared I had seen: “I’m going to be a pop star!” My heart pounding – not another wanna be pop star! Please don’t let it be true! My morbid curiosity aroused, I had to investigate – surely there was a painless explanation….

After a few minutes playing with GarageBand Arggg! Could this be any worse? What abomination am I about to subject my ears to? Do I dare click that link? I had to, I had to know just how bad it was. Hands shaking in fear of what I might hear, I clicked…. ba ba, da da da doo doo da My foot tapped, my head grooved. What just happened here? That was actually pretty good…. Is it possible that someone who so brazenly refers to themselves as a pop star could actually come up with a cool lick? What kind of wonder is this so called GarageBand? And how soon can I get a copy? So Matthew when do we get to hear your first complete works?

Well I’ve got latex installed – not at all easily I might add, but it’s up and running now. So I learn a tiny bit about the basics of Latex and start trying to focus my learning on the area I’m most interested in – writing play scripts. So I head off to CTAN (thanks to David Starkoff for pointing that one out) and find the “dramatist” package which appears to do everything I want. Download, install and everything looks good. Then I try to read the documentation…. Sigh. Apart from the use of narrative style which just makes everything exceptionally wordy, it doesn’t include a single example. No, here’s a pathetically simple script just so you can get your head around how to use this package, not even a ridiculously complex script to show off what the package can really do. Nothing, nada, zip. So now I have to learn the intricate details of Latex before I can do anything at all useful instead of just learning as I go along. So if anyone happens to have an example of a play script in latex (using any package) I’d love to get my hands on it…

Interesting article over at O’Reilly about the available Latex editors for OS X. It’s tempted me enough to have a play around. Well actually, the O’Reilly article gave me the knowledge to get started, this article gave me the reasons to do it. Since I’m getting into playwrighting I need to set up an efficient way of getting ideas down and being able to typeset them properly. I’ve currently got a Word template set up but Word X doesn’t seem to handle templates like it should and the layout is something of my own concoction rather than a standard layout. Hopefully I’ll be able to find a latex system to use and just go with that. Besides, you’re just not a true geek until you know latex….

Preparations for this year’s MarchFest are moving into full swing. MarchFest is a festival of music, art and and entertainment held every year at Kangaroo Point Uniting Church. We usually get a pretty sensational turnout of local Brisbane talent from a wide range of musical tastes, ranging from choirs and pipe organists during the afternoon in the church, to jazz, blues and rock and roll on the main stage and rocking on into night with punk, rock and alternative. So mark those calendars early, it’s always a good day. In the meantime, I’d better get to finishing the website for this year…

Okay, this is just scary. “SubEthaEdit virgin” – oh boy… Don’t worry Ted, what scares me most is that I understand perfectly. Sadly, I just don’t get enough SubEthaEditin’ in my life – maybe we need to start a SubEthaEdit brothel…..

Rick Jelliffe proffers his advice on how to write fast Java desktop applications. It’s poor advice. He calls his approach “defensive programming”, though I really don’t see much that’s defensive about it. Defensive programming is about adding in code to handle unexpected cases and recover from errors. Rick’s advice is an attempt at optimizing code before you’ve even written it and determined that it’s not fast enough. It’s worth noting that I write Java desktop applications, I don’t do much server side work and I certainly don’t write small applets, so Rick’s complaint that everyone assumes your a server side developer doesn’t apply here. It also doesn’t apply too much in real life – fast code is fast code. In desktop development you get more “time off” or more code that’s not on the critical path because you only need to go as fast as the user. On the server side you need to process pretty much everything as fast as you can because there’s always more requests to get started on if there’s a hold up with this request.