"An October 29 post by Bruce Haddon on an OpenJDK discussion list argues that the reasons for the separation of JavaFX from the JDK-namely, that JavaFX contributed greatly to the bloat of the JDK, that the separation allowed the JDK and JavaFX to evolve separately, and that the development and maintenance of JavaFX had moved from Oracle to Gluon-are much less applicable today."
"Further, it would be of great convenience to developers not to have to make two installations and then configure their IDEs to access both libraries (not really easy in almost all IDEs, requiring understanding of many otherwise ignorable options of each IDE),"
"It is both my belief and my recommendation that the time has come for the re-integration of JavaFX (as the preferred GUI feature) with the rest of the JDK."
JavaFX was removed from the JDK with Java 11 more than seven years ago. Original reasons for separation—contributing to JDK bloat, allowing independent evolution, and a shift of development and maintenance away from Oracle—are now less applicable. Modularization has addressed JDK bloat. Java and JavaFX releases have remained in lockstep and both projects are available in open source (OpenJDK and OpenJFX). Reintegrating JavaFX into the JDK would ease developer setup by eliminating dual installations and complex IDE configuration, maintain community involvement, and present JavaFX as the preferred GUI feature within the JDK.
Read at InfoWorld
Unable to calculate read time
Collection
[
|
...
]