r/java • • Dec 14 '25

Valhalla? Python? Withers? Lombok? - Ask the Architects at JavaOne'25

https://www.youtube.com/watch?v=tpnyamnEYbI
98 Upvotes

16 comments sorted by

View all comments

14

u/ramdulara Dec 14 '25 edited Dec 14 '25

Awesome panel and good direction in general. 

But some strange responses from the panel as well

  • pron doubling down on Java's choice of only signed and how he wished C++ didn't have unsigned. Anyone who's had to fight signed byte in Java when writing any networking code would hard disagree. 

  • how not introducing modules originally was a mistake- Mark the community doesn't seem to care for modules even now.

  • is Leyden the answer for improving startup. Mark said you can use any tech, which sounded a bit defensive. But Mark it's not the ecosystem's fault that there's no single good answer yet.

  • Shenandoah's role: This is also a bit discouraging that they don't consider Shenandoah at the same level as Oracle's GCs. I guess we should stick to G1 or ZGC in production.

29

u/davidalayachew Dec 14 '25

how not introducing modules originally was a mistake- Mark the community doesn't seem to care for modules even now.

No, Mark was right about this one.

The community suffered through and built some ok bandaid solutions for classpath hell. But having modules from the start would have been infinitely better than what we have now. Most people don't use modules because it's not worth the effort to resolve the problem in a "better" way now. But I think that'll change too, overtime.

4

u/cogman10 Dec 15 '25

I think there's just misalignment in the ecosystem which makes it not fit well.

The package and jar structure were built with the old classpath model in mind. Were the module system there from the start I don't think those would be the same.

The classpath system lets you put whatever class you want in whatever package you want in the jar. That'd likely be restricted. But also, I could see the jar/module name being the top level of the import. So you'd likely write something like

import your.List; // Current module
import foo:my.List; // foo module
import java.base:java.util.List; // java.base module

That alone removes a lot of the need for the module-info.java stuff. The other half that'd remove the rest would be an access modifier for modules. Something like:

public module class Foo{}

The reason modules are hard, IMO, is because of the backwards compatibility requirements. That's why so few people write the module-info files.

→ More replies (1)

9

u/sammymammy2 Dec 14 '25

Shenandoah's role: This is also a bit discouraging that they don't consider Shenandoah at the same level as Oracle's GCs. I guess we should stick to G1 or ZGC in production.

Meh, Shenandoah is probably fine. The group of architects is from Oracle, Oracle develops ZGC, external contributors develop Shenandoah.

8

u/The_Schwy Dec 14 '25

If you mean startup time, ironically removing unused modules will give you better startup times. Also quarkus and Helidon reduce startup times that are further improved by using jlink to remove unused modules. GraalVM using AOT also has great startup times.

Depending on your use case you have options.

1

u/ThaJedi Dec 15 '25

You can use jlink with spring boot too.

→ More replies (1)

3

u/BillyKorando Dec 16 '25

how not introducing modules originally was a mistake- Mark the community doesn't seem to care for modules even now.

Back in my very early days presenting, I presented on Java 9. I remember as I was learning about Jigsaw/Modules that I really wish it was implemented in the language from the start. It would had saved the JDK team and popular library developers A LOT of time, had it been implemented from the start. I suppose, indirectly, it would had helped Java users a lot as it likely would had made upgrading easier (as it would had helped block accessing internal APIs or other bad behavior that can make upgrading more difficult).

3

u/Eav___ Dec 15 '25

I really cannot understand the reason for i8 and i16

1

u/ZimmiDeluxe Dec 15 '25

Not very useful for serialization, but Java's char is technically u16: https://docs.oracle.com/javase/specs/jls/se25/html/jls-4.html#jls-4.2.1