Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Java 16

jdk.java.net

Post reply on HN
Print view View original

41–50 of 327 posts

Re: Java 16

#41

Post by mdaniel »

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"

There are plenty of languages which have contextually sensitive keywords for that exact reason. C# (a closer peer to Java syntactically) has contextual keywords including "var" and "notnull": https://docs.microsoft.com/en-us/dotnet/csharp/language-refe...

Re: Java 16

#42

Post by meddlepal »

vmception wrote: post #22
hasa wrote: post #6

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

yeah I'm confused too, so its because Java 9 officially came out September 2017 and they've been releasing very fast but have completely ditched semantic versioning chart here https://en.wikipedia.org/wiki/Java_version_history

Basically there's six month feature releases but every five or six releases there's going to be an LTS release. Most companies use the LTS releases. Next big LTS release is later this year.

Re: Java 16

#44

Post by meddlepal »

Freak_NL wrote: post #38
vmception wrote: post #22

Earlier quoted context omitted.

yeah I'm confused too, so its because Java 9 officially came out September 2017 and they've been releasing very fast but have completely ditched semantic versioning chart here https://en.wikipedia.org/wiki/Java_version_history

Java 8 → Java 11 → Java 17. Those are the LTS releases. If you want to follow a release cadence similar to Java 5 → Java 6 → Java 7 → Java 8, that's what you'll track. The intermediate releases can be used to test against, but adopting them too soon often means tackling lots of issues in your dependencies. And updating your application servers to a new major Java version every six months is not something you can do e…

If you're doing green field JVM developer and NOT using big frameworks like Spring or an app server it is pretty safe to use the intermediate releases.

Re: Java 16

#47

Post by Spivak »

throwaway4good wrote: post #34
btown wrote: post #16

Earlier quoted context omitted.

And now a 500 database error too!

There is an nginx in front of it. What was wrong with Apache?

Apache feels like a forgotten gem in the ops world. Everyone moved onto Nginx and at some point will run into some use-case that needs a feature that's only in Nginx+. And since Nginx+ is so expensive people end up just patching the OSS Nginx with the modules they need. But that whole time Apache was there with every conceivable battery and feature already included.

Re: Java 16

#48

Post by dweekly »

mdm12 wrote: post #27
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.

We see similar developments with C# borrowing features from F#, with records in v9, pattern matching, etc. While it's good for C#/Java, it does make it harder to push for adoption for a language such as Scala and F#. Why bother investing in the languages with a much smaller market share when the big boys adopt good bits and pieces from them constantly?

Really sorry to ask the dumb question here, but what is V9? A cursory Google search didn't show me anything about e.g. a major update to the V8 JavaScript engine?

UPDATE: Ah, C# v9.0 thank you all.

Re: Java 16

#49

Post by BoyRobot777 »

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.

Why not Kotlin, C#, F#, ML and so many other languages?

Re: Java 16

#50

Post by jmarcher »

meddlepal wrote: post #20
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.

Arguably, Kotlin took some of the better ideas from Scala.
Post reply on HN