Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:14134 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 89351 invoked by uid 1010); 21 Dec 2004 01:45:18 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 89305 invoked from network); 21 Dec 2004 01:45:18 -0000 Received: from unknown (HELO stack.fission.org.uk) (195.82.120.217) by pb1.pair.com with SMTP; 21 Dec 2004 01:45:18 -0000 Received: from bassman.fission.org.uk ([82.70.115.109]) by stack.fission.org.uk with esmtp (Exim 3.36 #1 (Debian)) id 1CgZ4l-00047F-00; Tue, 21 Dec 2004 01:44:36 +0000 Received: from 127.0.0.1 (AVG SMTP 7.0.296 [265.6.0]); Tue, 21 Dec 2004 01:44:39 +0000 Message-ID: <41C78007.2060300@fission.org.uk> Date: Tue, 21 Dec 2004 01:44:39 +0000 User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: George Schlossnagle , internals@lists.php.net References: <000601c4e6d2$6bda0f30$0100a8c0@pc07653> <41C74D41.7060608@lerdorf.com> <20041220222248.49013.qmail@pb1.pair.com> <41C776C4.70307@cschneid.com> <542F5DC0-52EE-11D9-B9E1-000D93359332@omniti.com> In-Reply-To: <542F5DC0-52EE-11D9-B9E1-000D93359332@omniti.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Why we =?windows-1252?Q?don=92t_like_PHP_/_?= From: gareth@fission.org.uk (Gareth Ardron) 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