Earlier quoted context omitted.
> but the chrome team is mostly reponsible for adding websocket, the file api, web workers... Oh, so these features are comparable in effort and scale to an entire web browser and HTML5-compliant rendering engine then? By your logic, Chrome is essentially KHTML + HTML5-fanboy-features. I guess that must mean Apple has been shipping a 2002-era build of Konquerer with each copy of Mac OS X then, huh? Because clearly We…
>Oh, so these features are comparable in effort and scale to an entire web browser Didn't Apple take the KHTML (Konqueror was a full fledged browser) code and then had to release their code because it was GPL. I remember reading about a complaint from the KHTML that Apple was releasing the code as a big blob and this was hindering KHTML integration.
WebKit has vastly evolved from the original KHTML library, to the point of being almost an entirely different product. The KHTML team has been pulling changes from WebKit (http://trac.webkit.org/browser) for many years now.