George Schlossnagle wrote:
At some point you'll have to face it: Apache 2 is becoming a popular "platform". It's obviously up to you at what point you'll consider this important enough to spend time on it but a reality check every so often is never a bad thing.
Not to sound overly American, but isn't this the sort of thing that's just worked out by market forces? When enough people want the apache2 sapi to be production quality, then eventually someone will become interested enough to do the work.
But isn't that exactly what is happening at the moment ?
Personally, I like apache 1.3.x. I like the way it does things, and it suits me down to the ground - but I can't ignore the fact that both redhat and suse are shipping with apache2 by default. Hell, even debian testing is apache2 by default now - and you all know how long debian take to pick up on something.
However, distributions are forcing this change no matter what people may or may not prefer. As such, rather than play catch-up when everything else fully supports apache2, doesn't it make sense to pre-empt that move towards a new sapi and make sure that php plays properly with apache2. I only suggest this because otherwise I see it putting people off php in the future. Put it this way, if you have a choice between php and perl, pretty similar in ease-to-learn and perl works properly with apache2 and php doesn't, which one are you going to pick ?
But that's just my 2c.
-- Gareth Ardron
-- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
