Re: GD vs Imagick
| From: | S.A.N | Date: | Wed, 16 Aug 2017 12:43:48 +0000 |
| Subject: | Re: GD vs Imagick | ||
| References: | 1 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-100226@lists.php.net to get a copy of this message | ||
2017-08-15 13:52 GMT+03:00 Rasmus Schultz <rasmus@mindplay.dk>:
> The following GD issue is all-too common:
>
>
> https://stackoverflow.com/questions/5773032/how-to-stop-gd2-from-washing-away-the-colors-upon-resizing-images|Ù
> o[80[�ÔÉ´[ù
>
> Basically anyone who's ever accepted uploaded images and resized or
> converted them, has bumped into this.
>
> Only Imagick makes it possible to work around this issue, it's not possible
> with GD, at all - and the internal behavior of GD is arguably "wrong", as
> the visible output of simply opening and saving a JPEG image with GD is
> mangled with washed-out colors.
>
> I am starting to wonder why GD is the default in PHP?
>
> It's a pretty outdated library with a clunky API - we have Imagick with a
> much more concise API and a ton more useful features.
>
> Why is the less-capable image library the default on the PHP platform? Why
> not Imagick?
Imagick - unsafe, slow and requires many external dependencies.
Now there are much better modules:
Vips - safe, much faster (7x) requires little dependency.
http://pecl.php.net/package/vips
It's better to spend your time on Vips , instead of having an Imagick
Thank.