A Twist of Citrus

Let's start with Internet Explorer.

I know that Internet Explorer has made awesome strides in the last 5 years in terms of taking up web published web standards, especially when it comes to things like CSS, which has removed a lot of hair-pulling on my part. Not that I really support MSIE anyway. I assume that in it works in Chrome and Firefox then it should work in MSIE, and if it doesn't then I feel sorry for the poor saps still using Internet Explorer and I move on, because the reality is that it's just too much work to develop for non-standards compliant browsers unless I'm being paid to do it.

Right now I'm working on a project at work that does require cross browser functionality, and I spent a good couple of hours trying to diagnose a javascript error in MSIE. (Infuriating in its own right. The error told me to look on line 108 in a 99 line document. This, despite the fact that I was executing javascript in a 39 line external file.) Anyone who has worked with the awesome javascript frameworks out there like MooTools or JQuery knows how amazing it is to live in a world where javascript runs pretty much uniformly across all major browser brands with little to no headache. I apparently managed to run across one of the exceptions to this rule. And it's such a stupid exception.

You can't use the following code to reset the page title with JQuery in MSIE.


The title tags are apparently an immutable node in the DOM in the world of MSIE. This bug runs from the earliest versions I could test in all the way up through MSIE 8. I couldn't believe it.

The solution:

document.title = 'Whoa!';

Yes, seriously. Screw JQuery's abstracted DOM editing glory, I had to regress back to perfectly average out-of-the-box javascript to edit the damn page title. Luckily it's a universally supported method of editing page titles so I didn't have to do any browser detecting nonsense. So there's your JQuery pro-tip of the day. Don't try to get clever with page titles, people.

Second order of business. I spend the better part of my evenings this past weekend writing up a pretty sweet little PHP daemon that can run constantly and check a secret e-mail address for new posts I want to e-mail in with pictures attached. It does some crazy processing and authentication to make sure I am not some spammer before it auto rotates and resizes images to fit into the blog and it even puts them in sane folders and it's all magical and object oriented.

I wrote all of this using a virtual Linux environment running in VirtualBox, and finished debugging it around 11pm last night. The previous post on here was actually a test I sent to the e-mail address which got automatically posted here on the blog. Awesomesauce.

Then GoDaddy happened. I host this domain and rdrkt.com on GoDaddy and pay a paltry sum once a month to do so. Thus far my experience hasn't been terribly infuriating, but when I went to upload my new Daemon, the code wont run because GoDaddy refuses to enable the IMAP extensions for PHP. Basically it's a big "F U we don't want you doing anything fancy with e-mail unless you pay us more money for a virtualized environment." I am not amused. I did a quick googleof the issue and there are lots of examples of folks whinging about them not enabling IMAP, and they apparently will only offer the reason that it is against their "security policy".

So I'm thinking about looking for a new host. I never really felt great about hosting with GoDaddy anyway, I don't like that their CEO kills elephants for sport, for example. And they generally come off as pretty evil if you read any accounts of folks trying to snag domains that are about to come onto the market. It all seems a bit like a racket, really.

So now I'm kind of kicking myself for not writing a commenting system, because I'd really love some advise on who to go with for hosting, readers. (If there are any of you out there.) Drop me a line via twitter if you have any ideas!