Existing users, 
Trimmit!
eliminating bloatware: delete junk files, clear resource forks, strip universal binaries...
Version: 0.95
Backup...
Feedback Type: Commentary
Contributed by: krishanuar Wednesday, November 28 2007 @ 03:30 PM PST
Product Platform: MacOSX
Used Product For: Less than a month
Correct me if I'm wrong, but doesn't creating a backup file defeat the purpose of trimming the app in the first place? If you are trying to save disk space, you aren't helping yourself by creating another copy of the file that you are trimming. Personally I think that the idea of having a blacklist/known list (like xslimmer) is slightly more intelligent approach. But trimmit! does seem to make the files smaller than xslimmer.
Backup... - cfrees
A backup is a good idea because then you can test the "trimmed" version before you commit yourself. If the application turns out to be one of the problematic ones that doesn't like being "trimmed", you simply delete the "trimmed" version and rename the backup; if, on the other hand, if the new version works fine, _then_ you can delete the backup and free up the disk space. This way you can try out the "trimmed" version before deleting the original.Reply to This
Saturday, April 05 2008 @ 04:59 PM PDT