> 1. It's WebKit itself or the way JavaFX wraps WebKit. > 2. It's the graphics layer of JavaFX that is not optimised enough yet. > 3. It's a 64-bit thing because JIT is not enabled in 64-bit WebKit (but why > does it only impact the JavaFX implementation?) > 4. It's simply because C++ is faster than Java. > 5.It's some other reason.
My first guess would be 2 or 3. It might be the way webkit calls web view, or the way web view calls prism. How is your CPU while it is rendering? For fun, turn on the pulse logger (-Djavafx.pulseLogger=true) and see what it says. Richard
