Previously, Melton explained how the Safari name came about, and the tale of Safari's User Agent string and the strategies his team used to keep the project under wraps.
Today, he shared details of the launch of Safari some ten years ago at the Macworld Expo in 2003. One of the more revealing sections of the piece looks behind the scenes at Steve Jobs' rehearsals for his presentation and some of the things that could have gone wrong.
Of course, thanks to Jobs' impeccable preparation, the Safari presentation -- and everything else that was revealed that day -- went off without a hitch.
Until I watched that video I found and posted of the Macworld keynote, I had completely forgotten what else was announced that day. Which is pretty sad considering I saw Steve rehearse the whole thing at least four times.The full article is worth a read for anyone who wants a peek behind the Apple curtain.
But you have to realize I was totally focused on Safari. And Scott Forstall, my boss, wanted me at those rehearsals in case something went wrong with it.
There’s nothing that can fill your underwear faster than seeing your product fail during a Steve Jobs demo.
One of my concerns at the time was network reliability. So, I brought Ken Kocienda, the first Safari engineer, with me to troubleshoot since he wrote so much of our networking code. If necessary, Ken could also diagnose and duct tape any other part of Safari too. He coined one of our team aphorisms, “If it doesn’t fit, you’re not shoving hard enough.”
Most of the time during those rehearsals, Ken and I had nothing to do except sit in the then empty audience and watch The Master Presenter at work — crafting his keynote. What a privilege to be a spectator during that process. At Apple, we were actually all students, not just spectators. When I see other companies clumsily announce products these days, I realize again how much the rest of the world lost now that Steve is gone.