Java desktop links of the week, March 12

Howdy folks! Big news this week, so let’s just get into it.

  • The big news this week was the announcement by Oracle that JavaFX is to be removed from the JDK from 11 onwards. This was covered in InfoWorld, and in a blog post and white paper by Oracle. In addition to JavaFX being moved to a module that is not shipped with the JDK, there were other Java client announcements made at the same time: Java Web Start and Applet technologies will also be removed from JDK 11 and future releases, and Swing / AWT, being a part of the Java SE spec, will continue to be supported through to 2026. For those of you forgetting the new release plan, JDK 11 is scheduled for release in September of this year. I have received a huge number of emails from people wondering what this means for JavaFX. The answer is – it is now in the hands of the community, with companies like Gluon stepping up to take on the load. You can choose to look at this optimistically (faster releases, easier contributions from community, etc) or cynically (another area that Oracle has abandoned and left the community in charge) – for me, I will write a blog post adding more detail about this as soon as possible.
  • Eric Canull has posted code to GitHub for a JavaFX-based sorting animation app.
  • Pedro Duque Vieira has updated his FXRibbon project to clean up API, etc.
  • Christoph Nahr has posted about Windows GUI DPI scaling in 2018.

3 thoughts on “Java desktop links of the week, March 12”

  1. Wow – this was not surprising but my thoughts based on the last few Java One was that Oracle might just give Java as a whole back to the community, not break out Java FX. Wondering if this was a deciding factor in your choice to leave Oracle? I am hopefully for more support and more tooling in the Open version of JavaFX going forward. Wondering if an application migrates up to JDK 11 but stays on the classpath if it will still be possible to get the new module, or if we need to upgrade to modules as well?

  2. The link to the blog post returns this right now:

    Internal Server Error – Read
    The server encountered an internal error or misconfiguration and was unable to complete your request.
    Reference #3.16962317.1521261503.42b3f05

    Gods of the server side are angry at Oracle 🙂

Leave a Reply