Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:130337
Precedence: list
MIME-Version: 1.0
References: <839153A0-004D-4562-BD6E-65923201EDAA@gmail.com>
 <299760A8-5C8A-41AD-B2EB-986079D41A47@rwec.co.uk> <4E9B666B-6EC5-48ED-849E-3E23F2041FF7@cschneid.com>
 <CAMW7n8AM5q4NLzoY=yY71HzSjH8qbUhTy4HLKJmpvYx4JuBXng@mail.gmail.com> <20260315134751.E25221A00BE@lists.php.net>
In-Reply-To: <20260315134751.E25221A00BE@lists.php.net>
Date: Sun, 15 Mar 2026 14:56:44 +0100
Message-ID: <CAKXKfQuSUvexD-NvztXmBZMDw05tU2+cMk5eJWkJbV6TToab=w@mail.gmail.com>
Subject: Re: [PHP-DEV] [RFC] php-community: a faster-moving, community-driven PHP.
To: Ben Ramsey <ramsey@php.net>
Cc: PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000a482a9064d107941"
From: daniil.gentili@gmail.com (Daniil Gentili)

--000000000000a482a9064d107941
Content-Type: text/plain; charset="UTF-8"

>
>
> Shared hosting companies aren't going to take that risk.
>

Arguments like these make me increasingly convinced that PhpFeatures should
just ship in normal PHP, without a separate distro.

Sandboxing offers all the needed security requirements, ensuring shared
host adoption while allowing frameworks to rely on feature extensions
shipped in normal PHP.


>
> Any company that runs an online business isn't going to take that risk.
>

Companies may or may not use those features, it is up to them.

What is important is that environments *allow* the usage of feature
extensions.

>
>
> PHP needs a much different ethos and ecosystem for something like this
> to work.
>

Talking about what the PHP ecosystem needs as a requirement for improvement
X will lead us nowhere, and is precisely the reason for this RFC.

--000000000000a482a9064d107941
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto"><div><div class=3D"gmail_quote gmail_quote_container"><bl=
ockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #=
ccc solid;padding-left:1ex"><br>
Shared hosting companies aren&#39;t going to take that risk.<br></blockquot=
e></div></div><div dir=3D"auto"><br></div><div dir=3D"auto">Arguments like =
these make me increasingly convinced that PhpFeatures should just ship in n=
ormal PHP, without a separate distro.</div><div dir=3D"auto"><br></div><div=
 dir=3D"auto">Sandboxing offers all the needed security requirements, ensur=
ing shared host adoption while allowing frameworks to rely on feature exten=
sions shipped in normal PHP.</div><div dir=3D"auto"><br></div><div dir=3D"a=
uto"><div class=3D"gmail_quote gmail_quote_container"><blockquote class=3D"=
gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-=
left:1ex">
<br><br>
Any company that runs an online business isn&#39;t going to take that risk.=
<br></blockquote></div></div><div dir=3D"auto"><br></div><div dir=3D"auto">=
Companies may or may not use those features, it is up to them.</div><div di=
r=3D"auto"><br></div><div dir=3D"auto">What is important is that environmen=
ts *allow* the usage of feature extensions.</div><div dir=3D"auto"><div cla=
ss=3D"gmail_quote gmail_quote_container"><blockquote class=3D"gmail_quote" =
style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br=
>
<br>
PHP needs a much different ethos and ecosystem for something like this <br>
to work.<br></blockquote></div></div><div dir=3D"auto"><br></div><div dir=
=3D"auto">Talking about what the PHP ecosystem needs as a requirement for i=
mprovement X will lead us nowhere, and is precisely the reason for this RFC=
.</div><div dir=3D"auto"><br></div><div dir=3D"auto"><br></div><div dir=3D"=
auto"><div class=3D"gmail_quote gmail_quote_container"><blockquote class=3D=
"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding=
-left:1ex">
</blockquote></div></div></div>

--000000000000a482a9064d107941--