Why the New JavaFX Makes Sense
Thankfully, Oracle recently changed course and turned JavaFX from a
dedicated language and a library to just a Java library (with some really cool stuff).
I welcomed the change and thought it was for the better, but my opinion
could not be called informed, because I had never worked with JavaFX
Script. Thus, I’m glad that I’ve recently come across a post from someone who has worked extensively with it and still likes the change. He confirms my suspicions:
- JavaFX Script was not as usable a language as Java: It was neither complete nor fast enough, and didn’t have the proper tools. JavaFX Script could have worked as a domain-specific language for Java, but the two were not well integrated.
- Other JVM-based languages benefit. With the new approach, the JavaFX functionality is available to everything that runs on the JVM versus to just to JavaFX Script.
(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)