I think the biggest difference is that I am using the chromium embedded framework (java-cef), so you get e.g. the chrome debugger for debugging your HTML/CSS/JavaScript.
My goal was to use java-cef, but hide all the weirdness.
Also, there's no pre-defined data binding, so a bit less opinionated in this case.
More performant? Maybe - at least multithreading, fork/join, ... would be easier.
Smaller binaries? No, probably even larger, since the chromium embedded framework (CEF) is biiig. But it would probably be possible to add other HTML renderers later (i.e. CEF during development b/c of the excellent debugging features, JavaFX WebView later).
It would make most sense when you either need multi-threading or have existing Java libraries/code you want to re-use or have mostly Java developers...
zubnix|6 years ago
struppi|6 years ago
My goal was to use java-cef, but hide all the weirdness.
Also, there's no pre-defined data binding, so a bit less opinionated in this case.
duiker101|6 years ago
gitgud|6 years ago
Would this be anymore performant than electron? Or smaller binary sizes? etc...
struppi|6 years ago
More performant? Maybe - at least multithreading, fork/join, ... would be easier.
Smaller binaries? No, probably even larger, since the chromium embedded framework (CEF) is biiig. But it would probably be possible to add other HTML renderers later (i.e. CEF during development b/c of the excellent debugging features, JavaFX WebView later).
It would make most sense when you either need multi-threading or have existing Java libraries/code you want to re-use or have mostly Java developers...
IloveHN84|6 years ago
unknown|6 years ago
[deleted]
struppi|6 years ago
But one could probably add other HTML renderers too (Android, JavaFX WebView, ...).