WebKit dropped: Google and Opera move to "Blink"
John_Smith at symantec.com
Mon Apr 8 15:14:53 PDT 2013
> I think this is going to be the big question coming out of the Google / Apple WebKit divorce proceedings. Google chucks a bunch of abstractions they don't need anymore to support Apple, Apple chucks a bunch they don't need anymore to support Google. Where do we end up?
Where we are today with a fork of WebKit specific for Java/JavaFX (http://www.oracle.com/technetwork/opensource/webkit-1667084.html) .
And that fork diverges further from the WebKit trunk over time.
Merges of changes from the WebKit trunk into the fork and vice-versa become more difficult over time.
Perhaps the fork starts diverging at a faster pace over the medium term as the Apple/Webkit/Google divorce plays out.
That's the thing about divorces, it's always the children that get hurt the most.
> The web view iOS support should be open sourced soonish I think.
Oracle have done more work on this than I expected :-)
From: Richard Bair [mailto:richard.bair at oracle.com]
Sent: Monday, April 08, 2013 12:28 PM
To: John Smith
Cc: Philipp Dörfler; Felix Kugel; openjfx-dev at openjdk.java.net
Subject: Re: WebKit dropped: Google and Opera move to "Blink"
>> Webkit engine feels slow and tries hard to render webpages strangely.
> I did some benchmarks on WebView a while back and it's performance and rendering capabilities were, in most cases for the benchmark tests I tried, perfectly acceptable for today's web pages.
I did a bunch as well, and found that on Java 8 we were about FireFox / Safari performance level.
Yes, I think this is going to be the big question coming out of the Google / Apple WebKit divorce proceedings. Google chucks a bunch of abstractions they don't need anymore to support Apple, Apple chucks a bunch they don't need anymore to support Google. Where do we end up?
>> Will we ever see something like the platform specific browser in JavaFX?
> I'm (wildly) guessing that if WebView ends up being supported on iOS, that might occur through wrapping the iOS Safari control rather than the ported JavaFX specific webkit engine modifications - but I doubt such a thing would happen anytime soon as there is no roadmap for such support and any initial iOS implementation for JavaFX is likely to go out without WebView support.
Actually that's exactly what we did, which is to use the built in JS engine. Anything else would run too slow (since apple doesn't let any other JS engine JIT other than theirs). The web view iOS support should be open sourced soonish I think.
More information about the openjfx-dev