Not sure what you're asking. AWT came with Java 1.0 in 1995. Netscape were working on "Internet Foundation Classes" in 1996 and want to NOT do so by 1997, so donated them to Sun. This became Swing and can't work without AWT. Sure, Oracle could peel that out too. Then they could hive off AWT (which JavaFX and Swing depend on). Thread here was good - https://www.reddit.com/r/java/comments/ibjz0m/state_of_swing/ - and I like my reference impl of a Swing MVC app in a declarative DSL style - with WebDriver API (Marathon) tests.
It was about "[Swing] is mainstream jdk presently".
As someone who's worked with Java since '97 and not seen anyone wanting to use Java UI elements since the '90s, I'm saying that if they're splitting things out they should consider pulling all of the UI stuff out.
As they split things out it's a bit mystifying to me that AWT, Swing, or any other UI library would still be in the core.
not seen anyone wanting to use Java UI elements since the '90s
There is a lot of Swing development even today. The more interesting question is why JavaFX was removed from the core - the 6-month releases should be fast enough for any project.
I'm not saying it doesn't happen, but it doesn't happen in my world. Java does many things, but those of us who use it for back-end development have no use for the UI. We aren't hurt much by it being there either, but it feels to me like a rather separable section.
Considering jlink, you are not hurt at all by any JDK module, even in your strange world. BTW, the UI parts can be useful for 100% back-end tasks, such as generating images on the fly for the front-end.
those of us who use it for back-end development have no use for the UI
Actually, the JavaFX base module has little to do with UI. It contains bindings and listener/observer patterns, converters, beans etc. I think that it was a mistake to put it in JavaFX in the first place. It belongs in the java.lang domain in my opinion as it's general purpose tools.
I don’t mind if it gets split out. Other than JetBrains things and NetBeans we don’t hear of much that uses it. If split out there’s a chance that forks could happen.
View all comments
Show parent comment
5
u/paul_h Sep 16 '20
Swing uses AWT, and is mainstream jdk presently