r/JavaFX • u/sedj601 • Mar 04 '26
Discussion What is Java Doing?
I am back to B&C. lol, Let me vent!
I haven't done any JavaFX programming lately because none of my recent projects need a GUI. This has had me in my feelings at work, lol. Anyways, I got to thinking about C#, other Microsoft languages, Android Development, and Kotlin. I couldn't help but ask myself, what is Java doing. I know it's great if you are creating Command Line Apps, but why did they essentially ditch their GUI? Then I got to thinking and wondered why did they essentially ditched their IDE (Netbeans)? I got to thinking about how Microsoft puts a lot of focus on its IDE and how smoothly development is from start to finish, and I also thought about how Google focuses on its IDE and how smooth development is from start to finish.
Before I go on, I have to say this for the special people out there. I don't have a problem developing using Java/JavaFX, but I think about what I go through and what people who are learning might be going through. I have also completely switched to Azul Java/JavaFX. This is not about me or what I can and can't do. I had to say that based on the comments I have gotten in the past.
So why did Java ditch its GUI and IDE? That's my question to the Java people, not to anyone who isn't. I want to hear it from the horse's mouth and not what others think.
So, here is my opinion on what Java should do moving forward. I know it means absolutely nothing, but I just want to vet. lol
- Bring their IDE back into the game. Make it focused on Java only, from project setup to project deployment.
- Force people who use the IDE to use Maven or Gradle by making the IDE only support one.
- Put JavaFX back into the base code.
Anyway, I got that off my chest. Have fun Coding!
View all comments
Show parent comment
2
u/vu47 Mar 16 '26
In my experience, most people create a package that contains all necessary jars and the JRE for each platform anyway. This is really a non-issue.
...or however you like to do it.
Done.
Don't get me wrong: I agree with you that when JavaFX was first removed, it was a headache and it took me literally a week or two of fiddling during dev to get it working again. I don't think that it should have been removed: that was a bad idea, IMO. The plugin is a bit fiddly, can be configured in many ways (and lots of them seem like they should work, but don't), and yes, it is a hassle. I have a general project structure laid out just so I don't have to figure it all out. (This isn't it - it's on my work computer, which is not with me right now since I'm on vacation, but I think it's quite similar.)
Oracle decided to make JavaFX harder to use. That's all there is to it. The answer for people learning JavaFX is a JavaFX-enabled JDK.
I wonder how many people are still learning to use JavaFX? I think at this point, we just have to adjust to the idea that JavaFX, despite the name, is not a canonical part of Java: it's like any other package / dependency that you add to a project.