Yep. I’ve got my very own nutjob on the internet who has decided he is going to go out of his way to fling poo at me! Seems like I did something to offend the, dare I say infamous, Rick Downes.

OK. I must admit when they were handing out the stalkers I wasn’t at the front of the queue. No Glenn Close (when she was still pretty darn hot) style femme fatales are after me alas. Instead I get some bitter, semi-retired Swedish geek who has oddly decided that I needed to be brought to task, for whatever it is I did to get his goat.

So who is this Rick Downes character? From his own site: “Rick Downes is an internationally acclaimed and respected computer scientist, long specialising in taking care of the ‘common man’ and in defending the rights of the common man against corporate and political abuses of power.” Go on, google him now, it should be easy to find some positive information on this person for who “hundreds of thousands of individuals worldwide know and well respect”.

Rick, who has a extraordinary fondness for using ©, ® and ™ symbols for ironic emphasis, apparently runs a software company in Cyprus where he likes to release poetry inspiring Mac OS X software (if you only follow one link from this blog post follow that one), has been arrested for commercial spamming and drug trafficking and has absolutely nothing positive to say about other people’s Mac OS X software.

Apparently I am in good company. Rick isn’t frugal with his diatribes against, well apparently lots of things. Rick dislikes a whole lot of things. And people. And software. And TIFF files. Rick especially dislikes TIFF files. Oh and bloat. He really doesn’t like bloat.

And what does Rick say about things he doesn’t like? Why, you get your very own page on rixstep.com where Rick will lay into you about how un-optimised your TIFF files are. He might even accuse of you of being a Texan (yes, really he believes someone who spells optimise with an S is Texan)! Or maybe he’ll call you a tool. Or try to disparage the work you’re doing helping to teach technology to children.

Rick seems to think he can use the internet and his professional web-site to attack whatever it is he doesn’t like. Generally he limits his attacks to software but occasionally he decides individuals are fair game. Unfortunately for Rick these attacks have done nothing more than turn him into a laughing stock amongst the developer community.

So what did I do to deserve the wrath of such a vengeful spirit? Well I participated in the comment thread of a blog post about software optimisation (yes, that blog post). That’s all it takes to unleash the bile and slobbering attacks. I may have also referred to Rick as a “911 conspiracy theory-level fucking nutter.” My bad. But then in my defence I was linking to this posting of Rick’s where he seems to go slightly off the rails about some conspiracy of the imaginary elite Mac developers, the so called “Landed Gentry of Mac Development™“ (note that the United States Patent and Trademark Office doesn’t seem to have that trademark on file yet, I can only assume the application is in the mail).

Rick started on me gently, merely (and quite randomly I might point out) mentioning me in his totally unbiased review of MarsEdit, calling me an “insufferable blogger”, amongst other things. I emailed Rick at this point to see if we could resolve this seemingly bizarre issue. But the chances are that my e-mail got deleted by his rather paranoid email filters (for a company that claims to pride itself on serving the customer I find it odd that e-mail from such large providers as gmail and mac.com are summarily discarded).

But then the big guns came out. Rick devoted a whole blog post to just me, or rather to “Johnathan Right” (a misspelling I can only assume Rick is intentionally making to be just that extra bit juvenile), linking to it from his Industry Watch page (yes really, slagging off a fellow developer is considered “Industry Watch”).

In the blog post Rick posts select quotes from a what was believed to be private conversation between myself and a 3rd party. Not quite sure what this has to do with, well anything really, but when someone takes the time and energy to write a whole blog post trying to character assassinate someone, rationality isn’t a priority. For some reason Rick seems to think a comparison between his qualifications and mine are in order. Bizarre! Batshit insane bizarre? Well go read the blog post. You be the judge. And of course Rick dredges up two applications that have long since been abandoned. Rick is nothing if not swift. By the way, Rick, have you ever considered abandoning some of your apps? Funny Haiku’s aside, some of your apps could really do with being taken out back and put out of their misery.

The funniest quote of the whole bizarre episode is “Ah Texas boy. We can relax. Texas has produced some ace programmers over the years. Like George Walker Bush.” Ignoring the half-arsed attempt at a Bush joke, Rick obviously spent 2 minutes searching my blog trying to find more mud to sling. And the best he could come up with is that I’m a Texan. Which of course, just happens not to be where I’m from at all.

I thought the Mac developer community had some oddballs in it before. But Rick totally takes the cake. A Mac software publisher whose catalog is so awful that there exists Haiku extolling their awfulness. A blogger who takes great pride in picking apart apps and slurring the developers of said apps with insults and ad-hominem attacks. Encouraging script-kiddies to deface websites. And let’s not forget the spamming and drug trafficking arrests.

So while I’m disappointed that my stalker isn’t a leggy blonde unafraid to do cruel things to bunnies, I must admit that as nutjobs go I think I’ve attracted one of timecubesque magnitude.

Of course I’ve committed the the biggest blunder on the internet: “Do not feed the trolls!”. Guilty I’m afraid. But maybe someone will hit this page while googling for Rick and realise what kind of person he is.

As anyone with a rather uncommon name can probably attest to, you just have to get used to people spelling or pronouncing your name incorrectly. Of course you can do your best to correct mistakes; back home I used to always say “Like the Isle of Wight” to help prevent error, but here in the USA that isn’t really so useful. My wife still gets annoyed at people spelling her last name incorrectly, but I’ve long gotten past that. Most people are happy to fix their errors when corrected and rarely make the same mistake more than once.

And of course there is occasional humour in someone intentionally misspelling or mispronouncing your name. Being referred to as “Jonathan Widget” never gets old. No really, it never gets old. Honest.

And still there are a plethora of alternative spellings for Jonathan too (all of them inferior of course) with “Jonathon” and “Johnathan” being perhaps the most common alternatives. But of course you pick your battles.

You’d think on the internet these mistakes would be less common. You certainly can’t blame these mistakes on mishearing the name. Generally the name is there, in ASCII form for you to see (or copy & paste), clear as day. But of course mistakes happen. On more than one occasion I have been confused online with Jonathan Wright, apparently an AI programmer at id Software. I would to think that Jonathan Wright has been mistaken for me in return. During a recent interview about Ironcoder I was quoted as “Jason Wright”, go figure.

It would take a special kind of Internet idiot to misspell a name more than say, a dozen times…

Toxic Progress Indicator should still be used on apps that need to run on 10.4, but I wont be supporting the class any more (not that it is really needed any support…)

Ask not what Ironcoder can do for you…

Unfortunately adding the cell caused drawing of the table’s window to slow to crawl. The spinning beachball of death would often appear when I was merely resizing the window. After some quick experimented I narrowed it down to something within the ‘Discrete’ variant of the NSLevelIndicatorCell, the other variants had no such performance problems.

It didn’t take an expert in Shark to realise what was going on:

It looked like NSLevelIndicatorCell was perform an expensive gaussian blur per cell, possibly even for each discrete block within each cell. For a single NSLevelIndicatorCell that shouldn’t be a real problem, but for a whole table column full of them it could create major performance problems.

Some quick google searches showed that people had complained about poor NSLevelIndicatorCell performance before but failed to find a solution.

Switching to another variant of NSLevelIndicatorCell wasn’t an option, the ‘Discrete’ variant was just too sexy. So the obvious solution was to create a subclass of NSLevelIndicatorCell that posed as the real thing, but cached the drawing code of its parent class into NSImages. So I present to the the world the imaginatively titled CCachingLevelIndicatorCell.

CCachingLevelIndicatorCell is designed to pose as NSLevelIndicatorCell but shouldn’t require any other configuration. The class will only cache images for the ‘Discrete’ variant and will use a dictionary of NSImage objects to cache the drawing (one image per discrete value the cell can display). If any other attribute of the cell is changed the class will discard the cache and attempt to recache the drawing at the next opportunity.

Just so you can compare the differences in speed I’ve created two stand-alone test applications so you can compare the speed without CCachingLevelIndicatorCell and with it posing as NSLevelIndicatorCell. The binaries are checked into my public subversion.

Radar bug: rdar://problem/4601201