CFV: New Project: Detroit

Alex Kashchenko akashche at
Thu Feb 1 21:46:08 UTC 2018


On 02/01/2018 07:52 PM, Hannes Wallnöfer wrote:
>> Am 01.02.2018 um 18:53 schrieb August Nagro <augustnagro at>:
>> Question: Would it be worthwhile considering WebKit over V8?
>> JavaFX already includes the WebKit-based WebEngine [1], which provides
>> "two-way communication between a Java application and JavaScript code," in
>> addition to rendering web content. Depending on only one native engine may
>> ease maintenance costs and additionally reduce download size (at least for
>> the JDK, given Jigsaw).
> That’s an interesting idea, but there are some problems with this approach.
> Most importantly, just executing a script and getting back the result is not enough, we need quite complex interaction with the JS engine to provide the level of integration we aim for. I don’t think we could piggyback that on the JavaFX WebEngine component without practically hijacking it. Even if we could, we’d then have to move in lockstep with JFX in terms of versions and configurations.

FWIW, WebKit JS engine - JavaScriptCore [1] can be used directly (not 
through WebEngine) - it has stable C API [2]. And besides being shipped 
as a part of JavaFX, it is also available in many Linux distros as a 
shared library [3].

But from description it looks clear that other JS engines besides V8 are 
out of scope for the proposed project, so this is just my 2 cents.

> Apart from these considerations, it certainly matters that Node.js is the most popular way of running JS in server/cloud environments, so using V8 opens a lot of doors.

Absolutely agree.

> Hannes



More information about the discuss mailing list