[webkit-dev] Deleting V8 bindings (was Cleaning House)
rniwa at webkit.org
Thu Apr 4 21:14:17 PDT 2013
On Thu, Apr 4, 2013 at 7:08 PM, Maciej Stachowiak <mjs at apple.com> wrote:
> On Apr 4, 2013, at 4:54 PM, Per Bothner <per.bothner at oracle.com> wrote:
> On 04/04/2013 10:21 AM, Oliver Hunt wrote:
> Supporting V8 places a considerable burden on webkit, there are a number of
> large, cumbersome and expensive abstractions required for to support
> JS engines (see the original discussions on the topic from many years ago).
> Nashorn: http://openjdk.java.net/projects/nashorn/
> This is for the WebView component of JavaFX:
> This is still experimental, and no committed deliverable. However,
> it is obviously preferable in the eat-your-own-dogfood way that we
> part of the Java distribution.
> This is still in pretty rough shape, but we would find it
> unfortunate if if becomes more difficult to build WebKit
> I created a new WebCore/bindings/nashorn directory in
> parallel to WebCore/bindings/js and WebCore/bindings/v8.
> classes" are ever created. Instead Nashorn provides an
> on-the-fly bridge to the Java objects.
> I think we'd be pretty reluctant to support this. Supporting multiple JS
> engines has been a pain, and we only agreed to it because it was a
> showstopper for Google, and we had the expectation that Google would be a
> valuable high-volume contributor. Which they were, during their time in the
> WebKit project. Even so, it caused significant code complexity, divergence
> of efforts, and friction on architectural direction, because of the
> differing characteristics of JSC and V8.
I'm with Maciej and others. There is a huge opportunity in front us to
improve the performance of WebKit by making more aggressive architectural
changes if we only had to worry about one JS engine.
On the other hand, I don't think optimizing WebCore for JSC doesn't
necessarily mean it'll become impossible for you to have a custom build of
WebKit that uses some other binding code. For example, Mac has Objective-C
bindings and that's not going anywhere in the foreseeable future.
- R. Niwa
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the webkit-dev