Earlier quoted context omitted.
> mogrify - resize an image, blur, crop, despeckle, dither, draw on, flip, join, re-sample, and much more. Mogrify overwrites the original image file, whereas, convert(1) writes to a different image file. The whole reason for mogrify's existence is that it overwrites the original image file.
> The whole reason for mogrify's existence is that it overwrites the original image file. Then it should not exist. To save one "rm", doesn't look like a good idea to me.
It definitely should.
This becomed critical when you are doing batch processing large amount of images in a cloud instance or somewhere else where disk space is a constraint.
I have used mogrify and similar custom solution when trying to batch-edit gigabytes of images while cleaning data for Computer Vision training.