Java 17 / JDK 17: General Availability
31–40 of 251 posts
Re: Java 17 / JDK 17: General Availability
#32On its own, the features specifically for Java 17 aren't obviously that compelling, but the important thing is that Java 17 is an LTS, the last one of which was Java 11, 3 years ago. Since many organizations, including mine, stick to LTS releases, that means a lot of developers will get a big change in what they can do sometime in the next few months as they upgrade to the LTS. Among other things, this means that we…
Re: Java 17 / JDK 17: General Availability
#33I am skeptical about the "strong encapsulation" and in general, of all cases whey people tell me about something: "you don't need it, it's better for you to do it other way". Usually I know better what I need. There were cases when I needed to access the internals, e.g. fixing a prod issue. A quote from Thinking Forth comes to mind: > The newest traditional languages (such as Modula 2) bend over backwards to ensure t…
Re: Java 17 / JDK 17: General Availability
#34Re: Java 17 / JDK 17: General Availability
#35I haven't touched Java since 8 but I'm itching to get back in it. Any good overviews of Java since 8 and what was added?
Re: Java 17 / JDK 17: General Availability
#36Earlier quoted context omitted.
Primitive classes are being worked on in Project Valhalla.
I think this statement has been true since about 2014. Structs are nice, as they allow for control over locality, to a degree that is simply not possible in Java currently. But there is a second effect, which is possibly more important: If I can move gigabytes of my data into arrays of structs, then 1) I greatly reduce memory requirements (far fewer pointers), and 2) I greatly reduce the amount of work that GC has to…
Re: Java 17 / JDK 17: General Availability
#37I am skeptical about the "strong encapsulation" and in general, of all cases whey people tell me about something: "you don't need it, it's better for you to do it other way". Usually I know better what I need. There were cases when I needed to access the internals, e.g. fixing a prod issue. A quote from Thinking Forth comes to mind: > The newest traditional languages (such as Modula 2) bend over backwards to ensure t…
This allows us to fix bugs in 3rd party software or the JDK itself until fixes can be released upstream and we don't wish to release an internal version of an artifact. Not something we use exclusively for obvious reasons, but it's a handy tool to have in the toolbox when we're forced up against a wall.
Re: Java 17 / JDK 17: General Availability
#38Are they going to introduce zero-cost structs? Kinda like Rust guarantees that Option has the same size as T (aka free like in free beer).
Re: Java 17 / JDK 17: General Availability
#39- (Proposal) Moving JDK LTS versions to a two year cadence [1]. Java 21 will be next LTS instead of Java 23.
- Oracle JDK is now free for commercial and production use [2].
- A new Java developer site [3].
[1] https://mreinhold.org/blog/forward-even-faster