You mean this?
Now Java supports top-level instance main methods and class-less compact files. That means now the following declaration is valid:
void main() {
System.out.println("Hello from Java 25!");
}
this post was submitted on 27 Sep 2025
42 points (95.7% liked)
Java
1820 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
I enjoy that the monstrous System.out.println is still right below. ๐
If you import java.lang.IO.println statically, you can simply write println
import static java.lang.IO.println;
static void main() {
println("Hello, World!");
}
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.
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.
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 becauseoutis already a field ofSystemrather than a package or type. It can be used to write it asout.println, but yeah, not much of a point anymore whenIO.printlnexists.
Static imports are only for static fields and methods. System.out::println is an instance method.
I'll be honest, I don't get the point of this feature. It's nice for beginners or for writing small, quick, programs...but for the overwhelming majority of all java code I don't see it being useful
the trend of serverless means that people are writing a ton more programs that are smallish single endpoint things. not that a ton of people are using java there, but that was a major motivation for c#
Sure, but I think the argument in favor of this feature is that the overwhelming majority of people picking up programming for the first time tend to be beginners, so if it helps them learn the basics before having to grapple with OOP then it is worthwhile.
Oh come on, please don't kill the public static void main(string args) meme!
Oh come on, please don't kill the public static void main(string args) meme!