| Really interesting comment! I tried to use JavaFX a while back and was really put off by it (whereas I've had good experiences in Swing). Some issues (it's been some time so memory is a bit hazy): - Lack of good documentation, both official and alternative (ultimately found a good reference book). - Lack of customization on some widget, even compared to Swing (remember being really disappointed at how hard it was to modify the built-in tab-view). - I really don't like the built not-quite CSS. Remember having trouble finding documentation for it. Also why a different language and not just code — like for the rest. - Was really put off by some parts of the API design, even compared to Swing. Something that I remember is that there was a half-baked support for "theming" that isn't really usable nor used. - This is much more debatable, and I won't wish ill on people who dismiss it, but it feels like it's completely out of the zeitgeist. I don't know if people doing unsexy jobs use JavaFX, but very people talk/write about it over the internet. Compared to Swing, the dearth of resources is staggering. It also created a lot of FUD that you can easily find if you google a bit. Don't use Swing cause it might be deprecated in favor of JavaFX (unlikely?). JavaFX hasn't really been updated nor hyped since Oracle took over, it's just rotting. IIRC it's not even bundled with the VM anymore, which is more headaches for distribution. Only exception: https://tornadofx.io/ has some love in the Kotlin community. - You have to link to different JavaFX jars for different platform, which makes any kind of Maven (etc) based dependency management a nightmare. |