4 ms·

> We had actually _just_ started a javaFX project only a few weeks before finding out it was removed. That project was binned and we went over to android apps i

by vips7L 5y ago

> We had actually _just_ started a javaFX project only a few weeks before finding out it was removed. That project was binned and we went over to android apps instead. You were going to start a _new_ project on an old runtime? There’s no logic here.

DarkmSparks 5y ago
javafx was released and pulled in between lts versions. introduced in 9 and removed in 11. https://www.infoworld.com/article/3261066/javafx-will-be-removed-from-the-java-jdk.html https://www.infoworld.com/article/3261066/javafx-will-be-rem... 11 is still the most recent LTS version, 17 doesnt even have a openjdk release yet never migrated to 11 because nothing we have running perfect on 8 ever passed its unit tests on 11. Even the 17 release notes basically seem to imply 17 is not ready for production.
- vips7L 5y ago
  But you’re making a _new_ project. Just make it on 11 and pull the openjfx jar into the build file.
  - DarkmSparks 5y ago
    It was a project started just before 11 was announced along with javafx's removal. Being removed meant any install on clients machines would be problematic (possibly why it was removed) So the project was reassessed, and everything that was going to use javafx was replaced with webkit/html5/css/js which was expected to be and turned out to be much easier to deploy and far far more portable.