I’ll admit, i have never really tested any website i created in safari. I don’t have an Apple computer, and i’ve never seen one at one of our clients. So no testing on apple. I would have, if i could run mac osx in vmware. But apple doesn’t allow you to vitualize mac os x. (With virtualization becoming such a big thing, i think this is a very bad decision by apple. But that’s a different story). But safari’s support for standards is pretty good, so i expect whatever works in firefox also to work in safari. Today apple released a beta of safari for windows, so now we can also test web applications in Safari. My first tests show that Safari still needs some work. The IT-eye website doesn’t work, google portal doesn’t work.
Why do we need another browser on windows? We don’t. But Safari is the runtime container for custom applications on iphone. Which means that developing for iphone will be a bit easier if you have safari running on your development machine. And apple wants developers for iphone, so i guess it’s in their best interest to have safari everywhere. It’s all about developers, developers, developers…

June 11th, 2007 at 22:09:39
And… Adobe AIR (formerly codenamed ‘Apollo’) is using the same WebKit rendering engine as Safari – on windows too – so yet another reason to test for it