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

Java 27: What's New?

loicmathieu.fr

Post reply on HN
Print view View original

31–40 of 64 posts

Re: Java 27: What's New?

#31

Post by OtomotO »

robertjpayne wrote: post #16
OtomotO wrote: post #13

Earlier quoted context omitted.

Unless you're forced at gunpoint, how can there be too many releases? Rust releases every 6 weeks, since 2016... If you don't want to update, just don't? If you feel (!) pressured, you should work on that.

Rust releases are just compiler toolchain, maybe some new syntax features. Java includes the JVM which is subject to way more security issues and needs much more frequent updating.

> Java includes the JVM which is subject to way more security issues and needs much more frequent updating.

Then releasing more often is better, because the security fixes get out of the door faster?!

If previously a Java Update took 3 years, then the corresponding JVM version would be 3 years old as well.

If there were patch release in between, I see no difference to now.

Re: Java 27: What's New?

#32

Post by samus »

bmacho wrote: post #14
this_user wrote: post #8

Earlier quoted context omitted.

It's too many releases now. At some points, the numbers just become noise. I think most people will stick to the LTS releases, but even those come out every two years.

The numbers have become meaningless noise already. This release should've been called 26.1, then 27.0, 27.1, 28.0 and so on. Year.version. How Canonical does it with Ubuntu. The current numbering scheme is annoying and distracting, bears no information yet is still error prone.

I believe that's by design: applications are encouraged to upgrade often. That's usually a smooth process for standard-conforming applications.

Applications that need to move slower can stick to LTS versions. LTS hopping has become a little bit more viable since the interval has been shortened to two years, i.e., four major versions.

Re: Java 27: What's New?

#33

Post by atomicnumber3 »

nerdile wrote: post #29

> tests showed that for environments with one CPU (or fewer) Article seems AI generated. Is there an official announcement we could be discussing instead?

I wonder if it's a joke about oversubscribed environments (cloud VPS) or a real remark about fractional CPU budgets in container environments

Re: Java 27: What's New?

#34

Post by speed_spread »

Borborygymus wrote: post #19

Java is swell and all, but having seen how the vendor treats even their large customers, I could never in good conscience recommend them to anyone I do business with. Better to miss out on the latest features and work with more respectful vendors IMO.

What vendor? OpenJDK is free and libre. If you mean Oracle, then that's a choice your employer made and yeah, you're SoL, especially for working in such a place.

Re: Java 27: What's New?

#36

Post by stanac »

UltraSane wrote: post #28
mountainriver wrote: post #24

The best thing to ever happen to the software world was Oracle buying Sun and consequently Java. Java was great at its time but then had to go. Oracle gaining control over them sped up this process. Poor Android got caught up and now half our phones don’t work

What are you trying to say?

I think they are saying Java is dead?! Not sure how else to interpret the comment. If that's the case I have to disagree. There are probably billions of lines of Java in enterprise, it will never die.

Re: Java 27: What's New?

#37

Post by samus »

wtetzner wrote: post #23
robertjpayne wrote: post #16

Earlier quoted context omitted.

Rust releases are just compiler toolchain, maybe some new syntax features. Java includes the JVM which is subject to way more security issues and needs much more frequent updating.

But can't you continue to run older bytecode versions on newer JVMs? I think you can also specify the source version separately.

Yes, you can. There is no need to recompile, unless you're interested in new language features.

Maintaining binary compatibility is a principal goal of the platform which continues to constrain design decisions for all future changes.

Re: Java 27: What's New?

#38

Post by stanac »

nerdile wrote: post #29

> tests showed that for environments with one CPU (or fewer) Article seems AI generated. Is there an official announcement we could be discussing instead?

It's probably comment on shared CPUs. Like in kubernetes where you can assign 300 milliCPUs.

I didn't read the article, it doesn't open for me (HN hug?).

Re: Java 27: What's New?

#39

Post by samus »

OtomotO wrote: post #31
robertjpayne wrote: post #16

Earlier quoted context omitted.

Rust releases are just compiler toolchain, maybe some new syntax features. Java includes the JVM which is subject to way more security issues and needs much more frequent updating.

> Java includes the JVM which is subject to way more security issues and needs much more frequent updating. Then releasing more often is better, because the security fixes get out of the door faster?! If previously a Java Update took 3 years, then the corresponding JVM version would be 3 years old as well. If there were patch release in between, I see no difference to now.

Patches are released continuously. The upstream versions get them immediately and they are then backported to LTS versions. Whether the patches actually become available simultaneously I cannot say without.

Re: Java 27: What's New?

#40

Post by UltraSane »

stanac wrote: post #36
UltraSane wrote: post #28

Earlier quoted context omitted.

What are you trying to say?

I think they are saying Java is dead?! Not sure how else to interpret the comment. If that's the case I have to disagree. There are probably billions of lines of Java in enterprise, it will never die.

Java is still very popular and even being used for new projects.
Post reply on HN