Post by Steve Drain
Memory saving is not a motivation. A relatively small but significant
speed gain might be.
Obfuscation of programs is, not necessarily for secrecy, but to prevent
users modifying programs and causing the maintainer problems when it all
goes wrong. The plain source might also be supplied for public programs,
but the crunching fixes a working version.
Thanks for making Crunchie, Steve. I've been a user of StrongBS in the past, which has its problems of course. I like StrongBS's rather extreme crunching and the little optimisations it performs. I'm into making little games and graphical demos, so program execution speed and high frame rates (preferably matching the screen/monitor's refresh rate) are fairly important to me. I know from some experience that crunching a BASIC program (via StrongBS) can mean the difference between, say, a 60 fps frame rate, and half that! Or the difference between a rock-solid consistent 60 fps, and an inconsistent 60 fps. So, yes, it can make a difference.
I haven't downloaded Crunchie yet, but I certainly will do.
I usually include the uncrunched versions of a program with the crunched one (the latter being the one that I want people to actually run). I'm not at all interested in obfuscating my (usually) crap code; I just want to give the interpreter a little less work to do.