Java 25 officially released

Post by SoKamil » Tue, Sep 16, 2025, 6:19 PM UTC

cgh wrote: post #63

lukev wrote: post #39

More new programs should be written in Java/on the JVM. Most of the reasons Java dropped out of popularity no longer apply, and at this point it is an incredibly stable and mature ecosystem. I can come back to a Clojure program I wrote ten years ago and it runs great , meanwhile a TypeScript program I write 6 months ago requires a bunch of updating and cleanup.

Java is hugely popular and widely used on large backend systems. I guess a lot of people here don't work on such systems? I'm always surprised when I see comments like the parent, since in my career exposure to Java is near-ubiquitous.

Post by jareds » Tue, Sep 16, 2025, 6:27 PM UTC

ohdeargodno wrote: post #58

jareds wrote: post #54

Earlier quoted context omitted.

I'm rooting against Kotlin since it appears to be only usable with the JetBrains ide. I'm totally blind and Jetbrains tools are not nearly as accessible or easy to use as VS Code with all the Java extensions in my experience. At all the jobs I've had no one cared if I didn't use Idea, but considering it looks like there's no good VS Code tooling for Kotlin if I have to use Kotlin professionally it's going to be painf…

As of somewhat recently, Kotlin has a language server: https://github.com/Kotlin/kotlin-lsp Using it in vscode, while not perfect yet, is starting to be alright.

Post by sorokod » Tue, Sep 16, 2025, 6:32 PM UTC

Sohcahtoa82 wrote: post #52

wry_discontent wrote: post #42

Earlier quoted context omitted.

In the circles I see, Java isn't popular because it's verbose and boring to use. These days I don't see those as significant issues, tbh. I would prefer a Clojure program, but I'll take Java over Typescript at this point.

> it's verbose and boring to use. Python code that follows traditional Python paradigms is called "Pythonic". Java code that follows Java paradigms is called "awful". To be fully transparent, I've never written Java professionally, only for a couple small hobby projects 10 years ago, plus some while in school, so my opinion isn't worth the pixels you're reading it on, but I look at most Java code with abject horror.…

Post by deepsun » Tue, Sep 16, 2025, 6:40 PM UTC

miki123211 wrote: post #30

(not a Java developer, no dog in this fight) I'm not sure I like the module import system very much. I think `import *`-like constructions make code a bit easier to write, but much harder to read, especially for developers new to the language / codebase. C# and Nim love that style, and it makes them almost unreadable without a good IDE. Personally, I much prefer Python's "short aliases" style, e.g. `import torch.nn.f…

Post by samus » Tue, Sep 16, 2025, 6:52 PM UTC

MBCook wrote: post #43

thewisenerd wrote: post #29

recently pulled the trigger on a migration out of jdk8 we decided to bite the bullet and do 21 instead of 17; one of the reasons being 25 being just around the corner. as far as i can tell, the biggest hurdle is 8 to 11 (with the new modules system); but it's smooth sailing from there. the proof-of-concept was done with jdk17, but it worked as-is with jdk21 (except guice which needed a major version bump). (of course…

For us 8 to 17 was tough due to a lot of things you weren’t supposed to be using going away (sun packages). But TONS of libraries did it anyway. And the move from javax to jakarta for a lot of things in there was also tough. If you could get through that, you’re golden. From what I’ve seen going to 21 or 25 look easy. They’re just adding features, the big upheavals of doing the long needed cleanup are over. I expect…