Java 16

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"

Re: Java 16

#5

Post by mooreds » Tue, Mar 16, 2021, 2:52 PM UTC

Super interested in https://openjdk.java.net/jeps/386 as alpine linux is at the heart of a lot of docker images. We use ubuntu currently as our base image, but tried to use alpine recently and ran into some issues with musl.

Hopefully this version will work better.

Re: Java 16

#6

Post by hasa » Tue, Mar 16, 2021, 2:52 PM UTC

OMG I'm old. I thought that Java 9 would be next version.

Re: Java 16

#7

Post by JCWasmx86 » Tue, Mar 16, 2021, 2:55 PM UTC

mooreds wrote: post #5

Super interested in https://openjdk.java.net/jeps/386 as alpine linux is at the heart of a lot of docker images. We use ubuntu currently as our base image, but tried to use alpine recently and ran into some issues with musl. Hopefully this version will work better.

I wonder, whether this could be used to compile it for termux. (Android)

You can link musl statically. So, the problems with Glibc wouldn't be there. Maybe you would have to patch musl to make it work on android.

Re: Java 16

#8

Post by whalesalad » Tue, Mar 16, 2021, 2:55 PM UTC

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

Re: Java 16

#9

Post by StepWeiwu » Tue, Mar 16, 2021, 2:59 PM UTC

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? :)

Re: Java 16

#10

Post by Thaxll » Tue, Mar 16, 2021, 3:00 PM UTC

Site is dying with 500.