JavaFX: Call to ARMs
justmy2bits.com
JavaFX: Call to ARMs
1–10 of 18 posts
Re: JavaFX: Call to ARMs
#2The WebView is just unusable. It segfaults the JVM if you use it wrong, and I had like three different ways I did that. It is practically impossible to control the behaviour of the navigation and Network fetching, which I really need to do.
Also it is just way to slow. All the widgets are coded like they are the only thing the app is for and contain huge object trees for the simplest blip. CSS support was (there have been efforts lately) just very clunky and half done.
Passing Events to/from a backend to the UI Model is still very clunky because of the Single Thread thing of the UI. It collides with the Binding semantics, which only really work inside one thread.
It really needs a slim down, and lots and lots of elbow grease to polish it into a state where it can be the base of a nice and big ecosystem.
The Design itself is rather modern and feels OK with Java8.
Re: JavaFX: Call to ARMs
#3Re: JavaFX: Call to ARMs
#4Re: JavaFX: Call to ARMs
#5[1]: https://en.wikipedia.org/wiki/JavaFX_Script
Re: JavaFX: Call to ARMs
#6The few customers that still require Java desktop applications have no desire to move away from Swing.
I really don't see a bright future for JavaFX.
Re: JavaFX: Call to ARMs
#7One irony regarding JavaFX is that the original JavaFX Script language[1] was probably among the best frontend languages ever created (better than TypeScript or Elm in many ways, IMO). It is powerful, typed, and easy for JS developers and designers to learn, plus it's designed for CSS integration. When it was abandoned by Oracle (good decision), it was forked [2], maintained and improved for some time, and then withe…
In my head it was destroyed by trying to improve it.
IIRC the first versions just worked and was amazing with live scripting etc. I even made an applet that was popular for a while.
Newer versions added more and more complexity before you could get anything done (again IIRC).
Feels a lot like Symfony: started small and focused and ended up as multiple smaller projects including a dependency inversion container but at some point along the road the magic was lost.
Re: JavaFX: Call to ARMs
#8Re: JavaFX: Call to ARMs
#9I wonder if he knows the fate of RoboVM.