TIL about gzexe.

Look up the manpage. It's most likely already on your machine.

It is terrifying.

This would've been really nifty in 1992, but *SO* out of place today.

@RL_Dane Oh, compressing executables still makes sense in *some* scenarios (relevant size reduction, not using a filesystem with transparent compression, "slow" storage media ...).

But then, #gzexe doesn't really cut it. It needs temporary files for decompression (spoiling most possible speed gains), and compression rates are mediocre. So *if* you have a use case for compressed executables, you'd better have a look at #upx, which achieves better rates and decompresses in-memory, in-place.

@zirias

Yeah, I didn't realize it was just a glorified shar. I thought they were doing some fancy-pants stuff.

Still, if it's 1995, and you have a lot of executables, it would make sense. ;)

@RL_Dane A use-case for executable "crunching" IMHO still valid today: somewhat larger "portable" (or better just statically linked) apps carried around on USB thumbdrives 😉

But then again, not so much for gzexe. But upx is really pretty nice.