81–90 of 101 posts
seeing ImageMagick, of all hoary tools, trending on HN reminds me that I'm so old that the kids are relishing as classics the tools I regard as outdated. This is expectable in music, but in tooling? And with Image -frigging- Magick ? Damn. Looking forward to the front-page HN-trended article on `sendmail`
See also vips and libvips, presenting a much cleaner library interface and faster processing: https://www.libvips.org/
I did a project where I scanned a bunch of old media. The scans where so high quality that it was impractical to make a PDF for people to use. The Imagemagick community helped out with the right incantation to make everything just kinda work. One of the rare cases where a project's maintainers will just help you use it. I was wowed.
I always found it fascinating the grade-A executable names which imagemagick was able to claim in the global namespace: imagemagick /usr/bin/animate imagemagick /usr/bin/compare imagemagick /usr/bin/composite imagemagick /usr/bin/conjure imagemagick /usr/bin/convert imagemagick /usr/bin/display imagemagick /usr/bin/identify imagemagick /usr/bin/import imagemagick /usr/bin/mogrify imagemagick /usr/bin/montage imagemag…
Earlier quoted context omitted.
Image magick isn't something you use frequently and quickly like changing directories or moving a file. A longer more descriptive name is better here. Also easier to speak. Telling someone to write "compare" is easier than "C-M-P"
I was trying to make a joke about the infamous naming practices of Unix, an operating system with a call named “creat”.
I always found it fascinating the grade-A executable names which imagemagick was able to claim in the global namespace: imagemagick /usr/bin/animate imagemagick /usr/bin/compare imagemagick /usr/bin/composite imagemagick /usr/bin/conjure imagemagick /usr/bin/convert imagemagick /usr/bin/display imagemagick /usr/bin/identify imagemagick /usr/bin/import imagemagick /usr/bin/mogrify imagemagick /usr/bin/montage imagemag…
This is something I always preferred about the graphicsmagick fork, was the `gm` base command.
I don't know about using a CLI to edit images, but one of the best thing of having imagemagick installed on my workstation (it's an absolute essential) is the 'mogrify' CLI tool to batch resize, manipulate or change formats of a whole directory full of images. https://imagemagick.org/script/mogrify.php
svgo (SVG Optimization)
colorist / avifenc (AVIF)
cwebp (webp)
convert (ImageMagick, everything else)
https://github.com/joedrago/colorist
There are 634 CVE Records that match your search. https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=imagemagick There have been a number of zero days. My entire interaction with Imagemagick has been removing it. Often with great difficulty because there is some odd dependency.
Imagemagick is one of the few bits of software where the functionality is worth the risk. Simply find a way to remove any network access and use it. I used to run it in a docker container with (almost) all capabilities dropped but with a directory mapped into it to run.
I always found it fascinating the grade-A executable names which imagemagick was able to claim in the global namespace: imagemagick /usr/bin/animate imagemagick /usr/bin/compare imagemagick /usr/bin/composite imagemagick /usr/bin/conjure imagemagick /usr/bin/convert imagemagick /usr/bin/display imagemagick /usr/bin/identify imagemagick /usr/bin/import imagemagick /usr/bin/mogrify imagemagick /usr/bin/montage imagemag…