OSNews > Thread > "RE[2]: existing apple ports don't measure up" by Adam S

Linked by Thom Holwerda on Fri 12th Jan 2007 19:03 UTC

A few days ago, Adam explained on his blog why it would make sense for Apple to port Safari to Windows: "Maybe it's making a leap of faith, and yes, the browser market is one where making a noticeable entrance will be challenging, but the less of a jump into the deep end buying a Mac is, the easier it is to make your Apple brand accessble, available, and not scary. The best way to start? Safari on Windows." Yesterday, Mary Jo Foley dug up from deep within Mozilla's Wiki the following prediction by the Mozilla Foundation: "Apple may have Safari on Windows with likely ties to iTunes and .Mac." This line has now been changed into a more general statement ("WebKit may be ported to Windows" - which already happened) but point remains: does it make sense for Apple to port Safari to Windows?

2 57 Comment(s)

http://osne.ws/d2b

Thread beginning with comment 201167
To view parent comment, click here.
To read all comments associated with this story, please click here.

RE[2]: existing apple ports don't measure up

by Adam S on Fri 12th Jan 2007 19:45 UTC in reply to "RE: existing apple ports don't measure up"

Member since:
2005-04-01

KHTML does not include everything in Webkit.

Reply Parent Bookmark Score: 1

RE[3]: existing apple ports don't measure up

by modmans2ndcoming on Fri 12th Jan 2007 20:29 in reply to "RE[2]: existing apple ports don't measure up"

Member since:
2005-11-09

So what. Why do you need a platform when all you really need is the rendering and standards?

Reply Parent Bookmark Score: 2

RE[4]: existing apple ports don't measure up

by Adam S on Fri 12th Jan 2007 20:32 in reply to "RE[3]: existing apple ports don't measure up"

Member since:
2005-04-01

I want be able to test safari specific CSS like the -webkit-* properties. It's easy to test the -moz* ones, but not the -webkit* ones. They aren't present in KHTML.

Reply Parent Bookmark Score: 1