CFV: New Project: Detroit

[Hannes Wallnöfer]

> Am 01.02.2018 um 18:53 schrieb August Nagro <augustnagro at gmail.com>:
> 
> 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. 

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.

Hannes