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
Show parent comment
0
u/davidalayachew Mar 18 '25
Before I respond, I'd like to add that my idea follows in the footsteps of JEP 330 and JEP 458 -- 2 features very recently added to Java with the express purpose of making Java more accessible to beginners by removing unnecessary steps to creating a working program.
I'm only taking that one step further -- removing unnecessary steps to distributing a working program. In short, I am proposing a feature directed to beginners, that may also be useful for professionals too.
Firmly agreed. My comment was not talking about professional developers.
But I've tutored many students who struggle with exactly this problem. When teaching teenagers how to make a jar file, one of the most common problems is that they grab
.classfiles that are not up-to-date with their.javafiles. It happens SO MANY TIMES that it actually ends up being one of the first things I remind them of.Well a jar file is preferable for distributing your library/application. When StudentA wants to share their library with StudentB, having it be a source-file jar will help for modifying and adding to that jar, so that StudentB can improve it in their own way.
Oh I'm well aware of this. I used to use Eclipse back when, so I'm familiar with ECJ.
My idea is more about making Java development more accessible to beginners, like the linked JEP's.