Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the 'Why are we all stuck on Stuffit?' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Why are we all stuck on Stuffit?
Authored by: avit on Jan 07, '03 09:16:17PM

Stuffit bugs me. It's the only compression program that isn't accessible from the command line. This tip will work only if the user is logged into the machine and can launch the StuffIt Expander.app. The whole point of the command line is that it enables the power of running tasks unattended or remotely. I can't expand a file if I'm not physically present at the machine to log in, and I can't schedule a cron job to do it either.

We can mount disk images. We can run installers. All remotely, or unattended! But we can't do the simplest task of unpacking a downloaded file! Shameful!

For OS X files, I can't think of a single reason to continue using .sit format files. Historically the format was helpful because it packed resource and data forks together for compression, but now that resource forks are becoming less prevalent, why use it? Why aren't we using a more universally accepted format like .zip or .gz, especially for simple things like .dmg files?



[ Reply to This | # ]