Critical deficiencies in upcoming Java module system (Jigsaw) (opens in new tab)

(developer.jboss.org)

3 pointswinteriscoming8y ago2 comments

2 comments

Sun/Oracle should have just swallowed their pride and standardized on OSGI as the Java module system years ago. Instead we've had years of back and forth, backbiting, arguments, and lack of progress... all the while people were actually getting work done by just using OSGI. At this point, the "standard Java module system" seems to be a solution looking for a problem.

shouldbworking8y ago

What is the point of the new module system? The current package system works fine. This sounds like it's going to break a bunch of stuff, particularly shading and dynamic class loading which I'm currently using.

Java should look at the C++ ecosystem. There's so much code already written that few sane people will use something that's not 99% compatible.

If you want to complete with Golang just make a subset of java that's AOT compatible

j / k navigate · click thread line to collapse

2 comments

mindcrime8y ago

shouldbworking8y ago

Java should look at the C++ ecosystem. There's so much code already written that few sane people will use something that's not 99% compatible.

If you want to complete with Golang just make a subset of java that's AOT compatible

j / k navigate · click thread line to collapse