this post was submitted on 27 Sep 2025
45 points (95.9% liked)

Java

1861 readers
1 users here now

For discussing Java, the JVM, languages that run on the JVM, and other related technologies.

founded 2 years ago
MODERATORS
Ategon@programming.dev
JackbyDev@programming.dev
thtroyer@programming.dev
45
I just started my first course without having to dismiss "public static void" in the first lesson as "we'll get to that later". I'm loving this. (sh.itjust.works)
submitted 3 months ago by abbadon420@sh.itjust.works to c/java@programming.dev
10 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] bradboimler@lemmy.world 3 points 3 months ago

Ah, interesting. I haven't kept up with the newest Java changes, so you kind of answered that backwards for me. Being able to just use IO.println() is already pretty good and for sure what I'd prefer over having to add an import. Seems to also be a new addition in Java 25, so I guess, Hello World looks a lot different all of a sudden.

My code was merely a demonstration that just println is possible now. Like you, I'd prefer IO.println in "real" code. My bar for static imports is extremely high.

Also interesting that this kind of static import doesn't work with System.out.println, I'm guessing because out is already a field of System rather than a package or type. It can be used to write it as out.println, but yeah, not much of a point anymore when IO.println exists.

Static imports are only for static fields and methods. System.out::println is an instance method.