Dave. Dave. What Are You Doing, Dave

Uh, Dave? Whatever you wanna call it, and however interesting, the question of what to render first and why—I was wondering if we could just fucking skip it and let Safari be the Bitch Queen she used to be?

'K?

And you got any questions on what's missing, we could start with:

Uno—I have not been able to upload anything anywhere with Safari going on two years now.

Dos—There's that little javascript problem, the description of which is over my head but you know, it's the one that never gets worked out, release after release after release.

And we could talk about KDE and whether there will ever be Rich Text editing in Safari, or little things I'm not supposed to care about, like Google toolbars.

Not that one wants to be like everyone else—Gecko, blech, except for Camino (how they do that?)—I swear, only a group of feature-starved Windoze users could get so excited about a freaky-looking mess like Firefox. Pink fairies? Race cars? Hell-o?

If I sound a trifle bitter, it's prolly the extra RAM to keep Camino running in the background, for whenever Safari does her random dance of “I Don' Know Nothin' 'Bout Renderin' No Java , Miz Scarlett.”

It's in there. I know it's in there. What I don't know is what in hell you WebKit guys do every day. While Firefox has extensions that answer the door and work on the Space Elevator, both at the same time ... I just want to use the Mac Browser of Choice. Cuz you know and I know, She has us both by the shorts; there isn't any question of a substitute—there are no workarounds for the best, Dave, She is the BQ.

Somehow I sense, clear as glass, without knowing a thing about your problems at WebKit Central, that there is only the removal of some layer of crap—experimental, busy-work crap—standing in the way of the smooth and speedy Bitch Queen living up to her interface once again.

I could be wrong. Though probably, in my witless intuition, not.