2
u/lpedrosa Sep 18 '20
Although the performance improvements on the GC are welcome, I doubt there will be a lot of uptake on this. And it will stay that way until 17.
The main reason is that a lot of folks don't understand the new release train. Also, the whole "LTS business" doesn't really help towards clarifying this.
I wonder what can be done in order for the community to overcome this.
2
u/nlisker Sep 18 '20
I keep being confused as to why people still don't understand the new release train and LTS. Ever since Java 9 the Java team has repeatedly explained this in talks, mails and write-ups. Mark has been giving the same talk for like 5 years now (including covering it again last week), several times a year. If people still don't get it, it's only because they didn't even try, and it's not even complicated.
27
u/__konrad Sep 15 '20
Release Notes: https://jdk.java.net/15/release-notes
New/removed APIs: https://javaalmanac.io/jdk/15/apidiff/14/ (additionally, some APIs introduced in previous versions are now non-Preview)
26
12
u/DJCowGaming Sep 15 '20
Yay! I have something to write about for my itgs class!
1
u/ILuvRiversHomo Sep 16 '20
What’s itgs?
4
u/DJCowGaming Sep 16 '20
Information Technology in a Global Society
16
u/jesseschalken Sep 16 '20
Sounds awful
5
1
u/franzwong Sep 17 '20
They reimplemented datagram socket api. Actually they did the same for socket api in 13 but I couldn't find any performance benchmarking about that.
4
u/TheCountRushmore Sep 17 '20
From the JEP
The microbenchmarks in the jdk/jdk repository include benchmarks for socket read/write and streaming. These benchmarks have been improved to make it easy to compare the old and new implementations. As things stand, the new implementation is about the same or 1-3% better than the old implementation on the socket read/write tests.
So I wouldn't expect to see much of a change either way.
0
0
Sep 15 '20
[deleted]
7
u/pron98 Sep 16 '20
JavaFX has never been a part of Java SE. It's an OpenJDK Project, but it isn't part of the spec, and is delivered separately. For some years it was bundled with the Oracle JDK distribution, that's all. AWT and Swing are an integral part of Java SE.
0
Sep 16 '20
[deleted]
0
Sep 16 '20
[deleted]
1
u/nlisker Sep 16 '20
There are dependencies on the Desktop module (AWT and Swing), so you can't remove them.
5
u/paul_h Sep 16 '20
Swing uses AWT, and is mainstream jdk presently
1
u/experts_never_lie Sep 16 '20
(implicit questions as to why that should be true)
2
u/paul_h Sep 16 '20
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.
2
u/experts_never_lie Sep 16 '20
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.
4
u/Necessary-Conflict Sep 16 '20
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.
1
u/experts_never_lie Sep 17 '20
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.
2
u/nlisker Sep 18 '20
those of us who use it for back-end development have no use for the UI
Actually, the JavaFX
basemodule 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 thejava.langdomain in my opinion as it's general purpose tools.→ More replies (0)3
u/Necessary-Conflict Sep 18 '20
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.
2
u/paul_h Sep 16 '20
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.
27
u/heliologue Sep 16 '20
Credit where credit is due to the OpenJDK folks keeping the release train running. Java hasn't felt this dynamic in years.