6 ms·

WebKit2 is a new API layer on top of WebKit, not a new browser engine. It has been used by Safari since v5.1.

• kibwen 14y ago
  Are you sure about that? When I read quotes like "web content (JavaScript, HTML, layout, etc) lives in a separate process from the application UI", that conjures images of a rather drastic and fundamental change. I'm not sure how you'd achieve that with just a new API layer.
  • bdash 14y ago
    Yes, I'm sure. The same core rendering engine, known as WebCore, is shared between both WebKit1 and WebKit2 on OS X. WebKit1 is used by most applications that use a WebView to display web content, while WebKit2 is used by Safari. The different API layers set up different delegate callbacks for WebCore so that they can tweak the behavior to fit their architecture (single process vs separate web and UI processes).
  • gcp 14y ago
    Firefox for Android does this, and it's not like the underlying Gecko engine is different.
    • khuey 14y ago
      Firefox for Android no longer does this, and hasn't since the "Native Fennec" launch.
      • kbrosnan 14y ago
        You two should hug this out in #mobile.