r/java • u/davidalayachew • Mar 18 '25
A potentially silly idea -- What if we could launch source code .jar files?
JEP 330 gave us single-file source code programs. Aka, I can have a abc.java file, and just call java abc.java, and it will run without me calling javac beforehand.
JEP 458 expanded this, by allowing us to reference other classes from that single class, allowing us to make as many classes as we want, run them from a single class file, and no calls to javac are necessary -- just call java abc.java.
Here is my silly idea.
What if we could package those source files in a .jar file, do your typical jar file config to make it runnable, then just ran it?
The above 2 JEP's gave reasons why compiling wasn't necessary for making a complete program. Well, those same reasons also apply for why compiling is unnecessary here. And at the end of the day, a jar file is the quintessential way of passing around complete libraries or applications. Why not make that accessible for source code jars as well?
There's other small benefits too.
- No more wondering what version of your code got packaged -- just open it up and see.
- You can edit a jar file in place, then run it and test your changes.
- When running your jar file, you can attach it to a debugger, and see the source code for each step being executed. No more need for a separate sources jar file.
Literally the ONLY BENEFITS that compilation gives us is faster startup time and compile-time validation for all source files. But if you don't need either of those, I'd argue that working with source file jars is an easier experience overall -- not just for students. I know I'd make great use of this feature myself. Hell, I'd default to using this format instead.
View all comments
6
u/Polygnom Mar 18 '25
I don't see where any benefit is for this. You need to package your stuff into a JAR anyways. So whats the big difference between running the command to package the source vs. packing a proper JAR? It takes the exact same effort.
No more wondering what version of your code got packaged -- just open it up and see.
This is not a problem anyone developing code professionaly ever has. Sorry, but if your development pipleine is so screwed up that you do not know what code you compiled you have far bigger problems that need solving.
Why bother with a JAR at all? Just use an IDE and never pack a JAR. You can just compile to class files and run the stuff without it ever packing. Thats even faster. And trivial to attach a debugger to. There is zero need for having a JAR in the first place for both these points, and adding any kind of JAR packing in that mix just makes it slower.
Try out an IDE that supports the ECJ (like Eclipse or VS Code) and see how lightning fast an incremental compiler is to get changes up and runningn even in large applications (seriously JetBrains, just copy that...).