coopster - 10:49 pm on Mar 22, 2011 (gmt 0)
hehe, great question alt131. Short answer? I did my research. At the time this was the best thing going. Smallest footprint (highest compression), most accurate. The bonus was ease of use (once you read all the documentation). But that's why I threw down the 3 steps, to save others time on how to use this utility.
I review my own processes quite often and am still using this effort. I wish Google would make their Closure Inspector and JS minifier easier to use in Page Speed. I need a tool that runs locally because my initial development is 100% offline. I don't have time to implement a FireFox add-on to minify my JS within the Add-ons available today. But one would think G could do that for you. I've seen quite a bit of back-and-forth in the G forums in this regard and eventually it will probably get to that point, but for now, I use that which is, IMHO, the best option.