Quote:
Originally Posted by Razor12911
288 - 119 = 169 KB, are you trying to fit the dll in a floppy disk or something?  |
Almost that...
If you only use a few libraries, that's okay with a larger size.
But when using multiple libraries it makes large sizes inconvenient for two reasons.
1. Setup.exe ends up getting bigger.
2. The extraction time of these compressors/libraries is longer.
With smaller sizes it is possible to use compression mode none (whitout compression) in Setup.exe reducing the time of extraction of these compressors/libraries.
To get an idea joining libraries and compression tools in the CIU source code and assuming that the creator of the conversion wants to make the option available to the end user to choose any of the methods supported by the ciu (Including all compressors/libraries) the size of the sum of these files is more than 50 MB (And there is another 6 MB of library files intended for graphics).
Yes, there are only a few Kb, but if each compressor/library has a gain of 150 Kb, it would reduce the final size considerably (in this situation there are more than 100 files). Of course, most of the time it doesn't.
Of course, if it doesn't work well it is preferable that it be bigger and without bugs.
As the friend commented, the idea is to have final sizes as small as possible from the installer + data file set.