Live data from Hacker News

Java 26 is here

hanno.codes

71–80 of 352 posts

Re: Java 26 is here

#71
post #37

the people that work on Java & the JVM are very smart. it has become a best of breed language - hell its better than Go for industry purposes. the drawback with Java will always be the CULTURE - (maybe someone can insert a quote of how in physics progress is only made, when old physicist die - I don't wanna be morbid ) but with Java same that's when the culture will change. All those people using typescript (could be…

Once i heard a manager explain "we must get rid of anything Oracle, including Java, because of license reasons". I see this attitude everywhere since.

JavaScript people are too afraid to use Java, that is why something like TypeScript exists.

And for personal projects, C# has become a better and more fun "just works" platform.

Re: Java 26 is here

#72
post #45

Earlier quoted context omitted.

"a solid foundation for the future" is faint praise for a language that has been around for over thirty years. > It has become a best of breed language To me it lags significantly behind .net (runtime) and C#/F# (language). I don't see Java catching-up.

They trade blows, and have different philosophies (complex runtime, simpler language vs the reverse). E.g. on the GC side Java is ahead of any other platform, especially with the low-latency ZGC garbage collector.

I would love to have a Java compiler with the capabilities of the .net compiler. To make incremental builds to aid code completion including type information, looking past simple syntactical errors, fixing them, and continuing compilation.

Currently, this is “magic” embedded in eclipse, IntelliJ, and maybe a bit in the vscode plugin. Imagine having a Java LSP running that can provide all this information while typing.

.net has had this for ages. From a language design I think that is wonderful.

Re: Java 26 is here

#73
post #46
post #36

Earlier quoted context omitted.

Are you perhaps confusing green threads with stackless async models, like async/await? Green threads don't imply colored functions.

They said "Java alternative for green threads" so they're talking about not green threads.

What alternative would they be referring to? Green threads were only (re-)introduced to Java in version 21 in 2023.

I think what they're trying to say is that Java's green thread implementation has special support for async I/O. Threads that block on I/O aren't polled for completion by the runtime, instead they use OS async features under the hood.

This allows Java's green threads to compete performance-wise with async/await solutions, but with cleaner code that doesn't need colored functions.

In older green thread implementations in other languages, I/O can actually cause significant CPU overhead due to polling threads that are blocked by I/O requests.

Re: Java 26 is here

#74
post #37

the people that work on Java & the JVM are very smart. it has become a best of breed language - hell its better than Go for industry purposes. the drawback with Java will always be the CULTURE - (maybe someone can insert a quote of how in physics progress is only made, when old physicist die - I don't wanna be morbid ) but with Java same that's when the culture will change. All those people using typescript (could be…

What do you mean by "better than Go for industry purposes"? I don't understand what "industry purposes" means and in what aspects Java is better than Go in your opinion (I can think of some myself, but I'm interested in your perspective).

Ya, that seems to be a misunderstanding. "Industry purposes" covers a huge range of stuff. Go is pretty good for systems programming where Java isn't really an option due to the fundamental limits imposed by garbage collection and lack of pointers. Java is pretty good for higher-level application development where occasional GC pauses are tolerable (the GC pauses are rare and fast now, but they still rule out using Java for certain purposes).

Re: Java 26 is here

#77

Do changes to Java itself impact e.g. Clojure? I think it uses many java primitives instead of emitting jvm byte code but I can be wrong.

In general, some java language changes do involve JVM changes.

So yes, it impacts other jvm languages like Closure.

Here most obvious would be GC improvements.

Re: Java 26 is here

#78
post #23

JEP 504: Remove the Applet API Glad to see this being removed. Java plugins especially on Linux were awful and required by tons of corporate stuff. Anyone remeber IcedTea Web? A functional and opensource Java plugin and Java Webstart implementation?

I made several Webstart corporate apps back in the day! The infrastructure was pretty neat, when it worked. And it was a whole lot better than JS back then, still in the IE6 times.

Yeah XMLHttpRequest and activex thing IE6 had. That was Javascript style that days.

Re: Java 26 is here

#79

JEP 504: Remove the Applet API Glad to see this being removed. Java plugins especially on Linux were awful and required by tons of corporate stuff. Anyone remeber IcedTea Web? A functional and opensource Java plugin and Java Webstart implementation?

Note that the the Java plugin and webstart was removed a long time ago.

I personally regret that the API was removed as it's a few classes and they are still used. Just search JApplet on Github. It's also possible to run applets in the modern browsers with WASM or in Java IDE's as plugin.

Re: Java 26 is here

#80
I haven't read a Java manual since the time of Java 8. Do you have any books or other resources you could recommend to catch up with all that has changed in these years?
Post reply on HN