Linked by Thom Holwerda on Fri 6th May 2011 22:13 UTC
Thread beginning with comment 472212
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/20/13 22:43 UTC
Linked by Thom Holwerda on 05/20/13 21:50 UTC
Linked by Thom Holwerda on 05/19/13 23:15 UTC
Linked by Thom Holwerda on 05/19/13 23:11 UTC, submitted by Drumhellar
Linked by Thom Holwerda on 05/18/13 21:06 UTC
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
Linked by MOS6510 on 05/17/13 22:22 UTC
Linked by Thom Holwerda on 05/17/13 22:15 UTC, submitted by Tom
More News »
Sponsored Links



Member since:
2007-12-10
The problem is that you're making an inappropriate comparison (which the original poster tried to point out above). Webkit is a rendering engine, Chrome is a browser.
Google never claimed to create a new rendering engine, because they clearly didn't.
Webkit, in contrast, is a project directly forked from an open-source rendering engine. Webkit is essentially a modified KHTML, where Chrome uses webkit as a library; different situations entirely.
Also, if you go and look at the contributors to Webkit, about a third are Google employees. So Google does openly support Webkit.