Saturday, April 6, 2013

Find: Google going its own way, forking WebKit rendering engine

This diversity will be good, and focusing in the code components chrome needs may also make it faster. 

---
 
 
Shared via feedly // published on Ars Technica // visit site
Google going its own way, forking WebKit rendering engine
Aurich Lawson (with apologies to Bill Watterson)

Google announced today that it is forking the WebKit rendering engine on which its Chrome browser is based. The company is naming its new engine "Blink."

The WebKit project was started by Apple in 2001, itself a fork of a rendering engine called KHTML. The project includes a core rendering engine for handling HTML and CSS (WebCore), a JavaScript engine (JavaScriptCore), and a high-level API for embedding it into browsers (WebKit).

Though known widely as "WebKit," Google Chrome has used only WebCore since its launch in late 2008. Apple's Safari originally used the WebKit wrapper and now uses its successor, WebKit2. Many other browsers use varying amounts of the WebKit project, including the Symbian S60 browser, the BlackBerry browser, the webOS browser, and the Android browser.

Read 10 remaining paragraphs

1 comment:

  1. This might be a great initiative for Google as they will tailor their own implementation in the best way they can. But sadly, to all those web developers out there, this will just create one more headache. Getting JavaScript code to work in the same way across multiple browser platforms is a pain and this will just compound that further.

    ReplyDelete