“On the contrary, Safari traditionally has been at the front of the pack in terms of CSS compliance”

You mis-read what I said, which is that it uses a rendering engine which has some CSS problems. See my original post for specifics. For a practical example, see this page in Safari/Konqueror and then Firefox/IE/Opera.

Also, you’ll notice that I already mentioned the iPhone earlier in the comments.

Finally, who bagged the iPod when it came out? People loved it from the word go!

What people like Mattew Magain forget is that they put lots of thought by many intelligent people at Apple. I’m sure they have their end goal, and worked on how to get there.

Apple will build some cool features into Safari. Think about a feature that lets people create iPhone widgets using Safari, just like in the Leopard preview for widgets on a Mac.

Soon you’ll have people installing Safari just after buying an iPhone. If millions of Windows users can put up with Windows, then Safari will be successfull, as long as Apple works to make it the best they can.

And I’m sure Apple have just ordered some Dell, HP, Acer to better test out Safari, because Safari for Windows on a Mac will probably always run the same, but it’s different in the Windows world where there are lots of hardware and software mix going.

Safari for Windows works well on my 2GHz Athlon machine.

People had so much valid points against the iPod, but the iPod ended up dominating.

Whatever you do, don’t bet against Apple and Steve Jobs.

Safari for Windows will get better (beta, remember?), but it won’t go away. The end game for Apple is measured in the billions of dollars, so you know it’s about something more than a free browser.

I’m pleased this has been released, it makes developing and designing a whole lot easier - now I no longer have to fire up the dreaded ibook…

Safari uses the KHTML engine, which has known problems with CSS.

On the contrary, Safari traditionally has been at the front of the pack in terms of CSS compliance. No rendering engine is perfect, and Trident (used by IE) is probably the least perfect of the lot (but getting better).

“Still, I presume this will be fixed by the time it’s ready for use.”

Maybe I presumed wrongly? Apparently, Safari uses the KHTML engine, which has known problems with CSS.

“Don’t get me wrong, I don’t like all of IE, either. But any traffic analyzer I look at tells me over 90% of the browsers used today are still IE.”

That seems pretty inaccurate to me. The latest browser stats at w3schools.com indicate that IE has less than 60% of the market.

Whether you set the value to “visible”, “hidden”, “auto” or ’scroll”, it treats it as “visible”. Which is horrible when your content includes source code listings, which typically use the <pre> and <code> tags.

Still, I presume this will be fixed by the time it’s ready for use.