On Wed, May 7, 2014 at 8:36 AM, Zeev Suraski <[email protected]> wrote:
>> On 7 במאי 2014, at 09:13, Sebastian Bergmann <[email protected]> wrote:
>>
>>
>> Playing devil's advocate: does anyone really need SAPIs other than
>> FastCGI, CLI, and embed? And if so: do we care enough to burden
>> ourselves with their maintenance?
>>
>
> I think you just called me "the devil" ;)
>
> Seriously, I can't think of any *real* reason of why anybody would
> need something other than these SAPIs in 2014 (other than FUD).
> Things like ISAPI and other more esoteric SAPIs are no brainers, and
> while mod_php may be a bit more of a leap of faith, it doesn't truly
> brings any tangible benefits over FastCGI (none that can't be
> relatively easily replicated in userland anyway, eg htscanner).
>
> I'd support it.
The problem here is not only the SAPIs but as a matter of fact Zend
cares about what they need and that's about it, and pushed things very
hard. We have to keep in mind that PHP success is not only based on
his design ( :-> ) but also because its availability on a large
variety of platforms.
If some likes to have a striped down (to one) set of platforms (in
this case, linux+gcc+fpm+cli), then go for it, the code is open and
there are many places where to host it. Facebook did it with many
other changes. But to restrict the future of PHP to fill some
individual needs (entities or person) is not a good thing, not for php
and certainly not for the communities.
Now, on a more constructive side, there are ways to improve the
situation and ease the overall development and maintenance work.
Droping TSRM or drastically improve it (TLS f.e.) could be one of
them.
Cheers,
--
Pierre
@pierrejoye | http://www.libgd.org