Java 16 • Hacker News Board

Re: Java 16

#11

Post by JCWasmx86 » Tue, Mar 16, 2021, 3:01 PM UTC

StepWeiwu wrote: post #9

JCWasmx86 wrote: post #2

The JEPs/enhancements: http://openjdk.java.net/projects/jdk/16/

The page returned a 500 for me, bad omen for Java 16? :)

The site works great for me.

Re: Java 16

#12

Post by dadoge » Tue, Mar 16, 2021, 3:01 PM UTC

Very cool to see that Scala continues to have a huge impact on Java’s roadmap.

Records and Sealed Classes are borrowed from Scala.

Could be not the best news for new Scala adoption, but good news for developers having better abstractions in Java

Edit: Kotlin, and other languages should also mentioned since they also include similar features. I still think Scala has had the most influence over the years.

Re: Java 16

#13

Post by Fiveplus » Tue, Mar 16, 2021, 3:01 PM UTC

Curious how many folks here experimented with the now depreciated Ahead-of-Time Compilation feature?

Re: Java 16

#14

Post by Erlangen » Tue, Mar 16, 2021, 3:01 PM UTC

java-man wrote: post #3

Why they decided to change the keyword rules to use "non-sealed" is beyond me. Surely, there might be other choices? Closed/unclosed? Unsealed?

It's the same story in C++, co_await, co_yield. The sole purpose is not to break other people's code.

Re: Java 16

#15

Post by Macha » Tue, Mar 16, 2021, 3:01 PM UTC

JCWasmx86 wrote: post #4

java-man wrote: post #3

Why they decided to change the keyword rules to use "non-sealed" is beyond me. Surely, there might be other choices? Closed/unclosed? Unsealed?

Yes. It feels out-of-place. All other keywords are like one word: enum, class, public, protected, native, sealed, ... But looks entirely different: Two words, connected by a hyphen. But I think, it was done because of backwards compatibility. If they would have called it "closed", it would maybe break hundreds of programs that have methods/variables called "closed"

I made this argument before, but was informed that they have support for contextually distinguishing between names and keywords some time between Java 8 and 10. So while e.g. the introduction of enum did cause all these issues for variables named enum, "var" did not and a hypothetical "closed" would not.

Re: Java 16

#16

Post by btown » Tue, Mar 16, 2021, 3:05 PM UTC

whalesalad wrote: post #8

I love the Java website. Strong early-2000s vibes. Still has an XHTML doctype!

And now a 500 database error too!

Re: Java 16

#17

Post by yellow_lead » Tue, Mar 16, 2021, 3:05 PM UTC

Records are a cool highlight for this version. https://openjdk.java.net/jeps/395

Re: Java 16

#18

Post by JCWasmx86 » Tue, Mar 16, 2021, 3:05 PM UTC

Fiveplus wrote: post #13

Curious how many folks here experimented with the now depreciated Ahead-of-Time Compilation feature?

I did experiment with it to improve the startup times of one of my applications (Java Swing). The gain was quite small, nearly not noticeable.

Re: Java 16

#19

Post by justin_oaks » Tue, Mar 16, 2021, 3:06 PM UTC

Thaxll wrote: post #10

Site is dying with 500.

Got the same at first. Reloaded the URL and it came up correctly.

Re: Java 16

#20

Post by meddlepal » Tue, Mar 16, 2021, 3:08 PM UTC

dadoge wrote: post #12

Very cool to see that Scala continues to have a huge impact on Java’s roadmap. Records and Sealed Classes are borrowed from Scala. Could be not the best news for new Scala adoption, but good news for developers having better abstractions in Java Edit: Kotlin, and other languages should also mentioned since they also include similar features. I still think Scala has had the most influence over the years.

I think the reaction has been more to Kotlin than Scala.