One Guy's Perspective on JavaFX
With JavaFX support waning within Oracle, let's take a look at what the future holds for JavaFX and how developers can get involved.
Join the DZone community and get the full member experience.Join For Free
I've had a lot of people ask me about JavaFX, especially with the recent changes announced by Oracle (there are a few follow-up articles at InfoWorld and jaxenter for more information), and on my leaving Oracle late last year. I've promised for a long time to add my thoughts to the discussion, but up until now, I haven't actually done so. Let me rectify that now...
For those of you that didn't hear the news, Oracle announced plans related to Java client. In short, some Java-client-related technologies will be removed from JDK releases. Of most interest is the fact that applets, Java Web Start, and JavaFX will no longer be available in JDK 11 and later. JDK 11 may feel like a long way off given how slow Java releases have been in the past, but remember that with the new release cadence in effect, we've already seen JDK 10 released last week, and JDK 11 is due out in September, I believe. This means that from September on, people downloading the JDK will no longer be guaranteed to have applets, Java web start, or JavaFX APIs available on their machine.
I poured my heart into JavaFX for a really long time — since mid-2009, it was my full-time job, firstly at Sun Microsystems and then at Oracle. It was a pleasure and a delight to work with so many smart, dedicated, and professional engineers during this time. I will always fondly remember the time I spent with them and class it as a career highlight. Equally valued by me was the opportunity to work with such a smart, motivated, creative, and dedicated community of people who were using JavaFX in all manner of projects. It was truly heartening to know that my code was being used to further science, to help send things to space, to trade in markets, to create mobile apps, and so much more.
At the same time, as an engineer working with so many truly excellent engineers, it was heartbreaking to see people leaving Oracle, but this was an all-too-common experience as budgets became tighter and tighter. Java is an open source project, with applications ranging from the smallest of profiles right up to hugely complex computing needs. It can be extraordinarily hard to monetize open source work, and it can, therefore, be challenging to justify continued investment into engineering efforts where there is no direct benefit. At the end of the day, my feeling is that JavaFX simply fell into this void — whilst there are some Oracle products using JavaFX, there weren't enough, and thus the justification for ongoing investment became a tough sell, with investment waning over time. Every time we lost some engineers, I felt that surely, we couldn't cut anymore — but I was all too frequently wrong.
That takes us to today. Oracle has made it clear that it is now in the community's hands to ensure JavaFX flourishes. The process for developing JavaFX itself is opening up, and simplification of the build process makes it more possible to become involved. Discussions are underway to move JavaFX into modules available via Maven repositories.
One day soon, JavaFX will be a compile-time dependency that you include in your build script. You won't care what version of the JDK your end-users have installed, because your build script will compile a native installer with an embedded JDK image, containing everything you need. Developers will create or coalesce around a new project for ensuring easy application updates. In other words, things needn't be so glum. It's a case of the King is dead, long live the King!
But challenges do abound. Unlike nature, JavaFX won't simply adapt for free. There is a lot that must be done, including all I wrote above. Beyond that, what is JavaFX? Who defines it and how does it evolve? How does it become something community owned? Is it forever bound to the OpenJDK, or does it transition to a third party (not unlike Java EE)? Community involvement at this juncture is critical — as the process opens itself up it also becomes ever-more dependent on those who form this community to bring their resources to the fore, or the risk is that JavaFX will wither and die.
In short, there are many ways one can choose to look at this announcement. I've had many more months to appreciate this plan than the wider community, but I feel like I straddle the entire emotional spectrum on this. It goes without saying that I would have loved to have seen Oracle growing investment in JavaFX, so there is sadness in me that this didn't happen. On the other hand, it is easy to see the lack of business sense in doing this.
I think my main emotion now is concern — I really do hope that the community steps up. If it doesn't, JavaFX will be no longer, and this is a real risk. On the other hand, if the community does step up (and I mean this extremely generally — I hope individuals bring their skills in coding, documentation, testing, advocacy, etc, but I also hope that deep-pocketed companies help to sustain these developers financially), then we may see something amazing happen. Already there are positive signs: Gluon has already worked with Oracle to create a repo on GitHub that enables community interaction and contributions, and there are a number of people already adding improvements into it.
I really hope we see something amazing happen.
I really, really hope that we see something amazing happen.
Finally, I feel like I should finish by saying: Java client was my home for a very long time. I've loved working with all of you, and I wish you all the best in everything you do. My time at Sun and Oracle was special. If you have the willingness to join in on JavaFX now, then you should reach out to the openjfx-dev mailing list. I will remain involved however I can (certainly with ControlsFX and Scenic View, and the desktop links post), but it is an outside of Oracle role from here on out.
Published at DZone with permission of Jonathan Giles, DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.