Today was WWDC 2007 in San Francisco, with Steve Jobs doing what he does best: standing on a stage and making several thousand people believe that whatever Apple was about to sell them was not merely desirable, but somehow inevitable.
There was plenty of Leopard, the upcoming version of Mac OS X, and naturally the iPhone, due to arrive on June 29. Cool stuff, certainly, but hardly shocking. They even managed to squeeze in the obligatory Steve Ballmer bashing, because apparently no Apple keynote was complete without poking Microsoft with a stick.
Then came the genuinely interesting bit. Safari for Windows. Naturally, I downloaded it immediately to have a look. Unlike my colleague Roger, I had no trouble with the installation. Safari fired up without complaint and it was surprisingly fast.
Of course, Apple couldn’t resist bringing QuickTime along for the ride. Because apparently installing one Apple product without being introduced to several of its relatives would have been considered rude. And then there is the interface. People call it slick, stylish, elegant. To me, it looks vaguely like Netscape wandered into a bar sometime around 1998, drank heavily for nine years, and came out wearing brushed metal.
Admittedly, my eyes are conditioned by spending all day surrounded by Windows applications, and I have no particular affection for the Windows GUI either. But consistency matters. When an application runs on Windows, whether Apple likes it or not, it gets compared with everything else running on Windows. Safari doesn’t merely look different. It looks like a Mac application that has somehow taken a wrong turn and ended up on my PC.
The Safari team seems to have gone to extraordinary lengths to make the Windows version look and feel exactly like its Mac sibling. Even the typography whispers Mac. For a moment you can almost forget where you are. Then you hit Alt-Tab and reality returns.
Mink Machine rendered in Safari browser.
Underneath all that polished metal is the important part: Safari uses the same WebKit rendering engine as the Mac version. For web developers, that’s where things become genuinely useful.
Am I switching browsers? No. I’m not climbing over the garden fence into Apple’s carefully landscaped little kingdom anytime soon. But having Safari running natively on Windows means one more browser in which I can test front-end code without borrowing a Mac, begging a colleague, or sacrificing livestock to the browser compatibility gods.
And in 2007, when making a website behave consistently across browsers occasionally feels less like engineering and more like black magic, that’s reason enough to keep it around.
Related posts
11 comments
Leave a reply