4 ms·

> Sigh. I had such high hopes for it, and then Oracle abandoned it. As far as I'm aware, it was only pulled from the JVM into a separate dependency, as did sev

• grandinj 6y ago
  Oracle has mostly disbanded the team that was working on it, leaving only one or two staff to manage community contributions. There are however, a couple of small companies, and some individuals using it, and providing contributions.
  • usrusr 6y ago
    Sometimes a setup like that is the best setup possible, no ambitious team trying to make their mark by replacing something that doesn't require replacing or that they can't replace well enough. I doubt that JavaFX would have more impact if they put a team of dozens on it (or, shudder, hundreds) but they would surely make life harder for those who still build on FX. A larger team might have already declared javaFX dead entirely, urging everyone to port to some exciting new javaFY and losing many of the remaining users in the process, without attracting any new ones. Arguably Swing to FX was already a bit like that.
  • vips7L 6y ago
    As far as I know Gluon has taken over the development of JavaFX.
  • fayten 6y ago
    Javafx is very much alive at: https://openjfx.io/ https://openjfx.io/ Gluon also provides builds for LTS and latest here: https://gluonhq.com/products/javafx/ https://gluonhq.com/products/javafx/
• cmiles74 6y ago
  It's not easy to get JavaFX working for development and it's tricky to get it bundled properly for deployment. I can see why they wanted to split out big parts of Java but I think it does discourage developers from using the library.