38 points 0x54MUR41 2 days ago 8 comments

giancarlostoro 3 hours ago | parent

Apparently JavaFX didnt die as we all thought back when Oracle spit it out of the JDK, they will happily offer support for it now, but who wants to be in bed with Oracle.

That looks really sleek. One thing JavaFX got right was CSS support.

geokon 3 hours ago | parent

JavaFX is supported by Gluon and not Oracle

pron 2 hours ago | parent

reactordev 1 hour ago | parent

It’s all a circle jerk in the JVM space

geokon 25 minutes ago | parent

Oh hmm, I'm honestly not super sure then. I know Gluon is the one that's seemingly has a business providing JavaFX support, while Oracle.. as far as I know doesn't offer a license or anything services in that direction? But I could be wrong. Gluon is mentioned in the article.. they have a very Qt-style confusing licensing situation where it's probably all free.. but you're never quite sure :)

The whole space is a lot more icky than one would like it to be.. Which is unfortunate b/c while it doesn't have a billion features, it's a nice composable reactive framework to use (at least from cljfx/clojure)

_benj 1 hour ago | parent

You see JavaFX everywhere in finance software. I learned it from working on finance.

pjmlp 47 minutes ago | parent

Everyone that uses Java, because Oracle is responsible for about 70% of development efforts.

https://insights.linuxfoundation.org/project/openjdk-jdk/con...

geokon 2 hours ago | parent

Thanks for writing this up! It still assumes a lot of prior knowledge, but it's a good starting point to approaching these problems. How JavaFX works on different platforms really looks like dark magic from the outside. I wrote an app in Clojure using cljfx. I can jpackage it and run it Linux/Windows/macOS .. it's quite easy to get working. But once you step outside of the standard platforms it gets complicated really fast. Trying to get it to Android or a native build and suddenly you have to be an expert in several build systems and JVM internals.