designate contact sierra-five

Turns out that I was a little wrong. The Japanese food wasn’t waiting for me at all, and it was the Buffy that was mediocre. Or worse. OK, yes, definitely worse. I’m trying to not imagine all those people out there who said “hey, maybe I’ll check this Buffy thing out” last night and will now never, ever return. Apparently one of my sisters-in-law has Buffy nightmares at times, and I think I might start as well. “God, will the Slayerettes speak again? Please, no, not more clunky exposition!”

I went into the office today, because the office is where I work. Ha ha ha. After most of a day spent unsuccessfully trying to concentrate enough to rewrite our connection-negotiation code, I finally gave in to the HISSING and the GROANING from the ventilation system, and the SHOUTING that said HISSING and GROANING requires of my office mates, and went home to nurse my headache. I’m working from home tomorrow, because home is where I can get some work done.

This whole Safari thing is a source of deep entertainment to me. I guess I’m supposed to be mortally offended — or at least embarrassed — that they went with KHTML instead of our Gecko engine, but I’m having trouble working up the indignation. We’ve all known forever that Gecko missed its “small and lean” target by an area code, and we’ve been slogging back towards the goal, dragging our profilers and benchmarks behind us, for years. If I had to write a new browser, and I was going to have to touch the layout code in a serious way, I would think about Mozilla alternatives. I think it’s awesome that they pretty much have to compare Safari to Chimera and Netscape/Mozilla, because it shows how far we’ve come from the universal acceptance of IE’s hegemony. I think it’s fantastic that they chose to include “Gecko” in their user-agent, so that they could get standards-compliant content, because it means that our evangelism efforts in support of such content have been working. I’m thrilled that they’re going to be another IE-alternative browser, which will try some techniques Mozilla decided against, because we can see if it really works or not. And I really really hope that Mozilla will learn from Safari/KHTML, because they’ve done a lot of great work in about a tenth of the code. Kudos, guys, and welcome to the web.

(I still think our JavaScript engine is better, though.)

I had to look at his in-development site to find Ian‘s email address, because it doesn’t seem to be anywhere on his current site. Dork.

Comments are closed.