TrimTheFat

Cut about 8 megabytes off of iTunes. 59 to 51MB. It works--and so does iTunes--so far.

good GUI on top of the trim command. simple, effective, no frills and free. One window, drag application, done. No buttons to push, no icons. You can't batch operations (as Xslimmer does), but it is not a real problem after all. start fast. maybe some preferences about the language to keep would be a good feature. if you want go the terminal route here is a good place to start http://lipidity.com/apple/cleaning-apps-mac-os-x/

Un vrai jeu d'enfant (même en anglais !), et pas mal d'octets dégagés en un clin d'oeil

It does one thing, it does it very well, it's under 1MB and it's free!!

Be careful of what you use this on...World of Warcraft had to be reinstalled after I used TrimTheFat on it (it wouldn't start up at all). That being said, it is pretty awesome - I saved over 1 GB!

Erm...cuts the file size "of apps" by half or more. I can't type today.

Works like a dream! Cuts the file size of by half or more.

I think I saved about a Gigabyte using this baby... I used it on every single app installed on my computer - even Apple programs (which had the most "fat"). My computer is still stable... and lean.

The blacklist has been updated to include Audio Hijack Pro 2 and Linotype Font Explorer X. Users can grab the latest version of the list by launching TTF, opening the preferences window and clicking the update button.

Although some app. don't like being trimmed for whatever reason, this Tool is GREAT! ¥ For rookies it creates a backup before trimming, cool! ¥ Simple interface, cool! And save lot's of disk space wasted on bloated applications! Very cool! Got back over 288 MB's in trimmings! Worked flawlessy with an eMac 384 MB's on Tiger 10.4.6 Keep up the great work!

"This is not a bug with Speed Download or TrimTheFat." I didn't mean to indicate that it was. A bug, in my book, is unintended behavior. As far as I can tell, Speed Download's behavior after trimming was quite intentional. "While some application work well; not all applications work well after they've been trimmed." In this case, the application apparently detects that the executable file (not code but file) has been modified and presents a message to the user asserting that it has been corrupted. There's no way eliminating code which is never even loaded into memory from the executable container should have any impact on the reliability of an app.