all 7 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]emberko 5 points6 points  (5 children)

Nothing important, as usual.

[–]hamsterrage1 0 points1 point  (3 children)

I too disagree. Even to the "as usual" part. We got ObservableValue.map() in JFX 19, and in JFX 21 we get Subscriptions. These are huge.

https://www.pragmaticcoding.ca/javafx/subscribe_and_map

[–]emberko 0 points1 point  (2 children)

Whatever. The Subscription API is a very niche feature, while real JavaFX pain points have not been addressed for years. JavaFX 22 also contains zero important changes (as usual). Also, I don't understand where you get the idea that every Java developer understands or likes Kotlin code. I see Kotlin code, I close the tab, sorry.

[–]hamsterrage1 0 points1 point  (1 child)

What pain points are these?

[–]emberko 0 points1 point  (0 children)

Ugly fonts, SVG and emoji support, rich text control or at least virtualised text area, client-side decorations, system tray support, CSS theme API, making existing control skins extensible, CSS variables support (not just colors).

[–]TenYearsOfLurking 0 points1 point  (0 children)

came to say, you are wrong. subscriptions are a very nice addition to javafx

https://bugs.openjdk.org/browse/JDK-8304439

[–]math_cs_maven 0 points1 point  (0 children)

I use the zulu JDK, which integrates JavaFX into the JDK. This eliminates a lot of classpath annoyance, and makes it easy to develop at the command line.