A modern programming language that makes developers happier.

kotlinlang

<@U25U0KPFT> I agree that it's easier to avoid shooting yourself in the foot with FXML. Builders require both some more constraint and also some more experience. I generally never add code inside the builder, and I think of the `override val root = buildMyUiHere` block in the same way as FXML. I also avoid having to mention all the ui elements using `@FXML/fxid()` because binding is done when I build the UI. I do add `setOnAction` blocks, but I always just call functions, so it is similar to FXML in that regard as well. FXML is a perfectly good way to go, and preferred if you have designers working on the app for sure.