This makes state and shared data management in JavaFX much nicer, as you offload those concerns to a container. CDI also provides extensive capabilities with portable extensions and scope management, as well as a sync and async eventing framework.
The problem is that I don't have a "real life" project to try this out on, so development kinda slumped off.
That looks really sleek. One thing JavaFX got right was CSS support.
Splitting it off the JDK was definitely the correct call. It's a Desktop UI framework, it should not be bound to JDK releases.
https://insights.linuxfoundation.org/project/openjdk-jdk/con...
That was forever ago, maybe it improved.
The whole space is a lot more icky than one would like it to be.. Which is unfortunate b/c while it doesn't have a billion features, it's a nice composable reactive framework to use (at least from cljfx/clojure)
There was a time Oracle decided it wasn't worth the investment, note that it started as E3 scripting under Sun and it was only finalised after the acquisition.
So a few Java champions took over it at Gluon.
Then when Java 26 was released, Oracle reintroduced support for JavaFX,
https://www.oracle.com/news/announcement/oracle-releases-jav...