Opened a leftover fortune cookie from last night’s dinner:

You have made a brilliant choice today.

Curiously appropriate.

Fun little blog entry documenting the life and death of a bug in Microsoft Word for Mac. A nice reminder of how difficult it can be to predict how your shiny new feature will interact with old code, and, more importantly, why it can take so darn long to fix an “obvious” bug. I’d love to see a similar explanation of Apple’s “can’t use capital U in firmware password” bug.

One thing this story doesn’t touch on is the importance of clear, unique error messages. If Word had actually reported “too many open files” instead of “disk full,” the problem might have been fixed a lot sooner. In one of my own favorite debugging stories, our discovery of the message “oh shit: fState != kParseError” led us directly to one line out of 16,000. It wasn’t clear, but it was at least unique.

"I downloaded the file in the hope that perhaps Microsoft had released some sort of public beta. The file unzipped, and to my delight the Microsoft icon looked genuine and trustworthy. I clicked on the installer file, and to my horror in 10 seconds the attachment had wiped my entire Home folder!"

Why, yes, Microsoft often officially releases beta software on peer-to-peer file-sharing networks. Your confusion is understandable, and no one is going to accuse you of being a software pirate. Really.

Besides, I’m pretty sure you won’t be downloading any commercial software in the future…

Update: Oh, and note the clever way the story implies that this had something to do with Intego’s “concept trojan horse” scare story. Sorry, Charlie, but we’re not that stupid. An application that doesn’t do what you think it will ain’t the same thing as an application disguised as an MP3 file.

Brian Tiemann went on a computer-free vacation right before the latest virus hit, and came home to more than 21,000 pieces of email. This has somewhat reduced his affection for Microsoft.

My first thought was to reply to his article via email, but fortunately I came to my senses.

So, Microsoft wasn’t shipping Java? Boo-fucking-hoo. Java on the web has been an insecure, browser-crashing nightmare from day one, and applications written in it are poorly integrated into native GUI libraries and sloooooooooow.

more...