4 ms·

I have been enjoying working on a cljfx project recently. Extremely fast to get a prototype together, proper multi core support for number crunching, whole JVM

by thom 5y ago

I have been enjoying working on a cljfx project recently. Extremely fast to get a prototype together, proper multi core support for number crunching, whole JVM ecosystem to reach out for functionality. Probably not for the faint hearted but it has the advantage that it exists today.

ducktective 5y ago
> Probably not for the faint hearted Any advantages over Qt or Electron?
- thom 5y ago
  For a Clojure programmer, yes. And for my particular use cases I’m happy with this over, for example, React Native plus ClojureScript because I can bring in JVM libraries and have easy threading. But if I were starting from a completely blank slate or building a startup around something (especially consumer based) I’d probably make different choices.
native_samples 5y ago
JavaFX is really under-rated. The primary argument against it being pushed by JetBrains seem to be related to exotic text rendering features, and/or bugs. OK, well, it sounds a lot easier to do some targeted upgrades there than throw it all out. The core tech is really solid. It's been neglected in the past few years but desktop tech doesn't change that fast. Throwing out a toolkit designed for complex desktop apps and trying to adapt a mobile toolkit doesn't seem likely to lead to better results.
- thom 5y ago
  I'll admit I learned JavaFX at the same time as the Clojure wrapper (which fights against the paradigm a little, perhaps) but what I've seen is fine. Big component ecosystem, and styling that appears to be quite powerful if you want it.
- billfruit 5y ago
  Main thing I feel concerned with JavaFX is that it is no longer being bundled with the JRE. Why is it not being considered a first class citizen of the Java Environment? This means that even the tiniest project using FX should have dependency management to ensure that JRE versions and FX versions and other supporting jars all align up properly to work. Meanwhile AWT/Swing just works right out of the box.

by thom 5y ago

ducktective 5y ago

> Probably not for the faint hearted Any advantages over Qt or Electron?

thom 5y ago
For a Clojure programmer, yes. And for my particular use cases I’m happy with this over, for example, React Native plus ClojureScript because I can bring in JVM libraries and have easy threading. But if I were starting from a completely blank slate or building a startup around something (especially consumer based) I’d probably make different choices.

native_samples 5y ago

JavaFX is really under-rated. The primary argument against it being pushed by JetBrains seem to be related to exotic text rendering features, and/or bugs. OK, well, it sounds a lot easier to do some targeted upgrades there than throw it all out. The core tech is really solid. It's been neglected in the past few years but desktop tech doesn't change that fast. Throwing out a toolkit designed for complex desktop apps and trying to adapt a mobile toolkit doesn't seem likely to lead to better results.

thom 5y ago
I'll admit I learned JavaFX at the same time as the Clojure wrapper (which fights against the paradigm a little, perhaps) but what I've seen is fine. Big component ecosystem, and styling that appears to be quite powerful if you want it.
billfruit 5y ago
Main thing I feel concerned with JavaFX is that it is no longer being bundled with the JRE. Why is it not being considered a first class citizen of the Java Environment? This means that even the tiniest project using FX should have dependency management to ensure that JRE versions and FX versions and other supporting jars all align up properly to work. Meanwhile AWT/Swing just works right out of the box.