Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:46525 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 22375 invoked from network); 27 Dec 2009 13:31:49 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 27 Dec 2009 13:31:49 -0000 X-Host-Fingerprint: 76.233.72.111 unknown Received: from [76.233.72.111] ([76.233.72.111:9236] helo=localhost.localdomain) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 61/16-26502-5C1673B4 for ; Sun, 27 Dec 2009 08:31:49 -0500 Message-ID: <61.16.26502.5C1673B4@pb1.pair.com> To: internals@lists.php.net Date: Sun, 27 Dec 2009 08:31:43 -0500 User-Agent: Thunderbird 2.0.0.23 (X11/20090817) MIME-Version: 1.0 References: <2dedb8a0911161713m5d8c3d3dma5013968d11f586f@mail.gmail.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Posted-By: 76.233.72.111 Subject: Re: [PHP-DEV] PHP6's future From: mwacker@cornellsun.com (Mike Wacker) Chris Stockton wrote: > Hello, > > On Mon, Nov 16, 2009 at 6:13 PM, Kalle Sommer Nielsen wrote: >> But what is every ones input on the matter of attempting to boost >> PHP6's development? I'm willing to give my part in whatever I can to >> help getting up on the feet to get this ball rolling. > > I think that some more focus on PHP6 would be great! Though I am not > sure if 5.2 could stop development (although perhaps a resource shift > to 5.3/6, starving new 5.2 features/backports for 5.2 security/bug > fixes only). I would hate to see PHP6 become P(erl)HP6 :p I have the same feeling on 5.2. While I'm very happy with PHP 5.3 (especially with the addition of closures), it takes a nontrivial amount of work to migrate a web app from PHP 5.2 to 5.3. The PHP 5.3 compatibility issue for the Drupal CMS (http://drupal.org/node/360605), for example, had over 200 comments, and it took about 9 months before a patch was committed to the current version of Drupal in September (see comment 158). That's not the only example, but it's a prominent one that comes to my mind. It makes sense to shift resources, but it's way too soon IMHO to stop doing security and bug fixes for 5.2.