on 2012-05-27 17:04 webfork wrote: Thanks for testing.
In my tests, PhotoScape (http://www.portablefreeware.com/index.php?id=1339) resizes GIFs reliably.
on 2017-03-23 21:15 philippe wrote:
Admittedly more powerful, yet please consider :
PhotoScape does weigh in at a hefty 23MB vs GifResizer mere 627KB...
@midason 2017-03-24 14:06 midas wrote: @__philippe:
that wondrous tiny footprint is achieved via UPX packing -- GiF Resizer unpacked is 2,014,720 Bytes. And BTW, unpacking and repacking with a current version of UPX might decrease its size further to 586KB (KiloBytes, not Kilobits;).
One point granted: Gif Resizer is indeed packed with UPX...checked.
Second point: PhotoScape distro itself is packed with NSIS - Nullsoft Scriptable Install System,
Now, if you'll humor me...
Instead of my early crude comparison of the packages gross footprint sizes
(i.e, the total size of every uncompressed distro components, as currently defined on the main entry),
let's compare exclusively the total size of every packed PE components of our contenders, that is Gif Resiser v1.10 (GR) vs PhotoScape v3.4 (PS)
- Packed exe+dll size (Bytes)
GR 642,560 GifResizer.exe
we still get a tidy 1/6 PE footprint ratio in favour of Gif Resizer (3,865,817 / 642,560)
What really ought To Be or Not To Be included in an app's SIZE field definition, That is The Question...
Currently, as I understand it, an app Size displayed on the main entry is calculated as:
"the total size of every uncompressed elements included in the distro package", right ?
For the sake of meaningful comparison between different apps, we might argue about the respective merits of using Alternative™ size metrics, for instance:
- 1. "total size of every and all elements - irrespective of any compression"
2. "total size of every PE file(s) (exe/dll) - irrespective of any compression"
3. "total size of every PE file(s) (exe/dll) - uncompressed"
4. "total size of every PE memory footprint"
- 1. Trivial - just look up the package external file size
2. Easy - add up the size of each exe/dll internal package components
3. Tricky - identify internal compressed components - decompress each candidate - add up decompressed component sizes
4. Moderate - load PE (run) in memory - from Win TaskManager: identify Process Image name - look up memory size usage