2 ms·
JavaFX is no longer part of the core OpenJDK distribution, but it's not dead and gone, it's just maintained separately. There's no need to stay on Java 8 to us
by MaxBarraclough 6y ago
JavaFX is no longer part of the core OpenJDK distribution, but it's not dead and gone, it's just maintained separately.
There's no need to stay on Java 8 to use JavaFX, although I'm not qualified to speak on whether it would be a lot of effort to upgrade a JavaFX application to a newer Java.
- fiddlerwoaroof 6y agoOne issue is that I think Oracle forced package renames and, afaik, there’s no compatibility layer available for packages that expected the old Class Names. To my mind, this sort of defeats the purpose of the JVM’s universally unique symbol names.
- MaxBarraclough 6y agoI don't think so. They were named javafx... both before and after, no? Doesn't sound like a real problem though. Renaming things is the easiest kind of change to accommodate.
- fiddlerwoaroof 6y agoI think I’m confusing it with the Java EE changes. However, renaming is only easy to accommodate if you have source access. The JVM’s model is portable binaries, so forcing renames breaks some of that model.
- MaxBarraclough 6y agoTrue, it would break binary compatibility.
- thu2111 6y agoJavaFX 15 API is compatible with that of JavaFX 8.