Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:100214
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain mindplay.dk from 74.125.83.42 cause and error)
MIME-Version: 1.0
Date: Tue, 15 Aug 2017 12:52:17 +0200
Message-ID: <CADqTB_hNm6ceRVyW9698_3v1qEtXC=uDLhiVzVcJ5y92aJTO+A@mail.gmail.com>
To: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="089e08284670b436330556c892b4"
Subject: GD vs Imagick
From: rasmus@mindplay.dk (Rasmus Schultz)

--089e08284670b436330556c892b4
Content-Type: text/plain; charset="UTF-8"

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

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?

--089e08284670b436330556c892b4--