3.6hours later.... nothing was written about grunt-imageoptim HOT 6 CLOSED

Hi @intellix,
Do you mean that the files are all the same size as each other, or as they were before they were run through the script?

The reason for ImageAlpha reducing the file size by more is that it is lossy, whereas ImageOptim is lossless (in quality).

Thanks.

from grunt-imageoptim.

Yeah, in the end it failed and it was like nothing happened.

I think it would be a good idea to split these two tasks so you can just run ImageAlpha if you want to save time. ImageOptim is the most resource intensive/time-consuming task out of the two so not too bothered about using it unless I'm going to run it whilst I sleep on large directories.

from grunt-imageoptim.

I wonder if this is related to #19 @intellix. If the job took 3.6 hours I'm guessing you were running this over a large set of files, is that right?

from grunt-imageoptim.

yeah, must have been a couple of hundred meg actually. That's why I decided to use a task :P

from grunt-imageoptim.

Ouch

from grunt-imageoptim.

Sorry for the huge wait, I will close this and instead track ongoing issues over at https://github.com/JamieMason/ImageOptim-CLI/.

from grunt-imageoptim.