Ok. What’s all the hoopla about Safari? Is it that Apple made it, or that it’s based upon KHTML? Really, what’s the big effin’ deal?

After gaining the knowledge that enabling error reporting in Safari really doesn’t do anything except give you stupid, vague errors, the idea hit me to use window.onerror. Surely if this browser is all it’s cracked up to be (I’ve heard nothing but good things about it), then window.onerror could give me a bit more insight in to the wonderful errors I see in the console.

<TenMinutesLater />

What the hell? Safari doesn’t even support window.onerror? But it supports the onerror event for images! This is almost as stupid as IE having makeshift support for PNG, and then having the code (through ActiveX) to display the PNG properly! The code is there; make it work!

Another thing about Safari: I was under the assumption (you know what they say about assumption) that it was just as good, or better, than Mozilla. Of course, this is coming from Mac and KHTML zealots, and I can’t even begin to think that it even comes close to topping Mozilla. My JavaScript works in Gecko and Trident, but yet it doesn’t in KHTML? Something’s wrong with this picture (it could be my code, but I highly doubt it).

So now I am faced with two options: spend countless hours trying to track down this “TypeError - Undefined value” with nothing but alerts() to guide my way, or cease trying to support Safari until Apple gets it to a decent level where it can be worked with.

Come on, Apple. If this is how you “Think Different”, then how the hell did you get this far?