4 ms·
> So if you don't use everything, your resulting Jar will be smaller I'll admit that I'm not super well-versed in Java packaging, but I kinda assume that typic
by zokier 9y ago
> So if you don't use everything, your resulting Jar will be smaller
I'll admit that I'm not super well-versed in Java packaging, but I kinda assume that typical jars do not include any bits from standard library, so modularizing standard library wouldn't have any impact on jar size. I'd imagine that the effect would be instead visible for self-contained distributions, like e.g. docker containers.
- needusername 9y ago> but I kinda assume that typical jars do not include any bits from standard library, so modularizing standard library wouldn't have any impact on jar size. That is correct. > I'd imagine that the effect would be instead visible for self-contained distributions, like e.g. docker containers. In theory. In practice you need to build a JDK contains only the bits you need. Sounds great in theory, you can get rid of the CORBA and GUI modules, that should save you a lot of disk space. In practice the CORBA module is only 2.7 MB and the desktop module is 14 MB and almost every framework indirectly requires the desktop module because Java Beans are in there.
- concede_pluto 9y agoOne of the worst things about the Docker fad is that people are wasting effort minifying things like the JRE and libc so that having many copies on the same machine isn't quite so blatantly foolish. They could be accomplishing something but instead they're wallowing in a problem that was solved decades ago.