What are Leyden's plans to minimize application footprint, specifically disk footprint?

[David Alayachew]

Hello,

I don't know where this belongs, so please redirect this as needed.

I am working on building an executable for my Microsoft Paint clone, and I
used jpackage to do it. My module-info.java only had java.base and
java.desktop, but the generated binary (after running the installer) was
~71MB. Thanks to a helpful answer on Stackoverflow (
https://stackoverflow.com/questions/78308134), I was able to bring that
down to ~49MB using --jlink-options --compress=zip-9. I was grateful for
that.

But a double digit sized executable generated from <3000 lines of Swing
code with no resources was a bit difficult to swallow.

Obviously, those 3000 lines house a lot behind the curtain.

* There's the 2 modules -- java.base and java.desktop. Unfortunately, they
also happen to be the 2 biggest modules in the entirety of the JDK.
Sometimes, I wonder "Why are they that large? Could they have been broken
down further? Might that happen in the future?"

* There's also the Operating System specific files. I see 1MB dedicated to
just awt.dll, for example. I am Windows 11.

* And then there's the jvm itself, which is a whole 12 MB on my machine. It
seems to also be a dll.

All of this is what is created when I run the installer. So it all makes
sense, and I don't think any of these components are being needlessly
included.

But I still want to know -- what are Leyden's plans to minimize application
footprint, specifically disk footprint?

Thank you for your time!
David Alayachew
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/leyden-dev/attachments/20240411/d39dd15c/attachment.htm>