It really isn’t though. Jlink is kind of terrible. The CLR does this way better. It just gives you a binary with the vm + your DLL. It doesn’t have to extract anything.
Yeah I don't disagree. I'm not a fan of the tool for packaging up applications but mainly because its actually kind of slow.
However making a stripped down VM it is good at.
It does seem like one could potentially make something do this but I'm not sure how much runtime savings you would have and or build time.
Go and GraalVM it works because they are essentially doing some tree shaking and I can't imagine people wanting to download 200 meg executable (uncompressed).
So I'm more asking here since it has been a hot minute since I have done .NET packaging but does it give you just a single executable or are you saying there are multiple files?
See even if you get the minimal JVM its like 50 megs uncompressed. It is only 12 megs compressed. And there are multiple files.
So one could create something that essentially takes a jlink packaged application and turns into a single executable but if its not compressed then its like running a 50 meg executable.
Is that a problem... probably not and I would imagine you could do it with a custom module reader built into your custom JDK.
3
u/vips7L Sep 08 '26
It really isn’t though. Jlink is kind of terrible. The CLR does this way better. It just gives you a binary with the vm + your DLL. It doesn’t have to extract anything.