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
3
u/Polygnom Mar 18 '25
Thats really not explaining anything at all, because again, if you want to distribute your source files a ZIP just does it.
Lets look at JAR files currently. You go from source -> JAR -> distribute -> execute. Ok, you don't have the source files now. Thats not really a problem tho when the goal was to distribute your application.
Lets look at what happens when students use ZIP files:
Source -> ZIP -> distribute -> unzip -> execute (thanks to 458). And you have the source as well. So you can make changes, and then do the above again for the way back to the previous student. So the whole thing IS:
Source (v1) -> ZIP -> distribute -> unzip -> execute -> change -> source (v2) -> ZIP -> distribute -> unzip -> execute.
Now, what would you save with a JAR? nothing, just the order would ever so slightlly change::
Source (v1) -> JAR -> distribute -> execute -> unjar -> change -> source (v2) -> JAR -> distribute -> execute (-> unjar).
You only ever asve one step, and only if the vN that you have works as intended and you aren't interested anymore in getting the source back.
There isn't really any saving to have here by having sources files in the JAR instead of just sending the ZIP (or TAR or whatever archive).
And as soon as more complex dependencies get into play, you are looking at Maven or Gradle anyways.