Newsgroups: php.general,php.internals
Path: news.php.net
Xref: news.php.net php.general:325701 php.internals:95472
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.220.178 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CACMzB5fobnzNHGkRdB90qtjOMEb4imzAZ1ZmCaJE16eJJRDi+Q@mail.gmail.com>
References: <CACMzB5ccYey3m2h_eWzk+okDXy0ANWXD4M-Yv0JfJu2i=FMWnA@mail.gmail.com>
 <5E615A59-AC2B-455F-9438-D295419F3767@ashleysheridan.co.uk>
 <CACMzB5cjhfs0s88ohW=Rq4DA2-2dv1-EKGt7ZWnSLT8Sb0OvKw@mail.gmail.com>
 <33E6F0A8-A14B-4590-A18C-FF6D6E029D0A@gmail.com> <CACMzB5dUfmWofWWq379tmnqYQ69XjAWs8PLv12Jct2NrNaczhw@mail.gmail.com>
 <3B285FFA-4C62-421D-A5B5-E5F205C53C02@gmail.com> <CACMzB5ehV9iB2NWtfH7qNzacu-OXMagDAJ82iQCX-OknEXxTtw@mail.gmail.com>
 <A5DD1C35-57B9-446C-B884-46979AD28DEC@ashleysheridan.co.uk>
 <CACMzB5d_EMqa7-OvgoYndbDi0jvfTw--viW=0L3PjK=Tm_v=3w@mail.gmail.com>
 <93D96A8A-0AFA-4378-B3F1-E7CA8E68C8B6@ashleysheridan.co.uk> <CACMzB5fobnzNHGkRdB90qtjOMEb4imzAZ1ZmCaJE16eJJRDi+Q@mail.gmail.com>
Date: Sun, 28 Aug 2016 03:26:21 +0200
Message-ID: <CACMzB5cCcfBO1umc7a76q6bOs9_3h=xpwAdZZdQaGK+pKqj_iw@mail.gmail.com>
To: php-general@lists.php.net, internals@lists.php.net
Content-Type: multipart/alternative; boundary=94eb2c07e5b6c976f8053b17a35f
Subject: Fwd: [PHP] feature request : gzip caching
From: rene.veerman.netherlands@gmail.com (Rene Veerman)

--94eb2c07e5b6c976f8053b17a35f
Content-Type: text/plain; charset=UTF-8

---------- Forwarded message ----------
From: Ashley Sheridan <ash@ashleysheridan.co.uk>
Date: Sun, Aug 28, 2016 at 3:03 AM
Subject: Re: [PHP] feature request : gzip caching
To: Rene Veerman <rene.veerman.netherlands@gmail.com>


Please don't top-post.

Nginx was probably suggested as a lightweight web server, instead of
Apache. I can't say I've ever seen both used at the same time.

Any developer who is serious about their career has an understanding of how
web servers work and the server caching capabilities. If they don't, I
think it's fair to say they're still pretty junior and ideally would be
helped by a more senior developer.

I struggle to understand why you're making PHP responsible for trying to
cache js files that are only requested by the front end. It feels like
you're overcomplicating things somewhat.


---------- Forwarded message ----------
From: Rene Veerman <rene.veerman.netherlands@gmail.com>
Date: Sun, Aug 28, 2016 at 3:24 AM
Subject: Re: [PHP] feature request : gzip caching
To: Ashley Sheridan <ash@ashleysheridan.co.uk>


i'll top-post whenever i like.. don't tell other ppl how to format
documentation / discussions, please.

and to answer to your comment : i strongly disagree. it makes sense for
those working on complicated webapps to limit the number of knowledge pools
they must master and keep up to date..
hell, i dont even get into canvas and webgl because the knowledge domain is
so large and different from *my domain*; HTML, JS, CSS, JSON..
seriously, you can not expect complicated beautiful apps to be written for
browsers until you recognize that limitation on human ability..

--94eb2c07e5b6c976f8053b17a35f--