Newsgroups: php.general,php.internals
Path: news.php.net
Xref: news.php.net php.general:325706 php.internals:95477
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.220.182 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <BA6AED75-E8FD-4F7B-9A70-9A63CE532BD1@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>
 <CACMzB5cCcfBO1umc7a76q6bOs9_3h=xpwAdZZdQaGK+pKqj_iw@mail.gmail.com> <BA6AED75-E8FD-4F7B-9A70-9A63CE532BD1@gmail.com>
Date: Sun, 28 Aug 2016 03:39:03 +0200
Message-ID: <CACMzB5cRo6bGVoeKTPqikrx1O6Nnd0F3QZPvsQYBa4hy1ns1Yg@mail.gmail.com>
To: Joshua Kehn <josh.kehn@gmail.com>
Cc: php-general@lists.php.net, internals@lists.php.net
Content-Type: multipart/alternative; boundary=001a114fe870352ce4053b17d1f6
Subject: Re: [PHP] feature request : gzip caching
From: rene.veerman.netherlands@gmail.com (Rene Veerman)

--001a114fe870352ce4053b17d1f6
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

with all due respect, you sound like you don't know what you're talking
about ok.. i rest my case at the arguments i presented, confident it'll
convince the internals team (which is what this is *about*, ok)..

On Sun, Aug 28, 2016 at 3:37 AM, Joshua Kehn <josh.kehn@gmail.com> wrote:

> On 27 Aug 2016, at 21:26, Rene Veerman wrote:
>
> 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 h=
ow
> 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 poo=
ls
> 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 fo=
r
> browsers until you recognize that limitation on human ability..
>
> Works on =E2=80=9Ccomplicated webapps=E2=80=9D and =E2=80=9Climits number=
 of knowledge pools=E2=80=9D are
> opposites. You need to find the right tool for the job. In this case, PHP
> is not the right tool.
>
> --jk
>

--001a114fe870352ce4053b17d1f6--