Re:Dependency
by detaro on Monday August 17, 2020 @09:10PM
(#24194268)
Not the parent poster, but it does a lot and is a regular source of potential security issues, and there's always a worry you haven't turned off everything you don't need etc. So if I process external inputs and don't really need ImageMagick, I prefer using more limited pieces.
[ Parent
| on HN ]
Re:Dependency
by WesolyKubeczek on Monday August 17, 2020 @09:23PM
(#24194353)
Yeah, the frequency with which they have to make security patches is telling a lot about the overall code quality.
One might argue that it's because it's more popular than other similar projects, but it doesn't happen as often with, say, Pillow. And I don't quite remember PIL/Pillow having holes as big as ImageMagick.
Also, try actually programming against it. Whatever language you choose, it's going to feel clunky and alien. It feels alien in C. It feels alien in Perl. Even in PHP, the match made in hell, it feels thoroughly un-idiomatic. I'm not even surprised they have to patch it up now and then.
Parsing complex untrusted inputs in a language that isn't memory safe is the center of the unholy venn diagram. It's very hard to do a good job under those conditions.
While "rewrite it in Rust" is a cliche, I think ImageMagick is a good candidate!
I think it's a thing! https://github.com/imazen/imageflow
Re:Dependency
by WesolyKubeczek on Tuesday August 18, 2020 @04:06AM
(#24196295)
Can it easily sprout bindings to other languages, especially given Rust’s ABI stability guarantees which are as firm as melted icecream?