Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:65316 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 48444 invoked from network); 29 Jan 2013 07:12:15 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 29 Jan 2013 07:12:15 -0000 Authentication-Results: pb1.pair.com header.from=larry@garfieldtech.com; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=larry@garfieldtech.com; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain garfieldtech.com from 66.111.4.29 cause and error) X-PHP-List-Original-Sender: larry@garfieldtech.com X-Host-Fingerprint: 66.111.4.29 out5-smtp.messagingengine.com Received: from [66.111.4.29] ([66.111.4.29:42370] helo=out5-smtp.messagingengine.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 5E/24-28517-C4677015 for ; Tue, 29 Jan 2013 02:12:13 -0500 Received: from compute5.internal (compute5.nyi.mail.srv.osa [10.202.2.45]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id DFA3C2066F for ; Tue, 29 Jan 2013 02:12:09 -0500 (EST) Received: from frontend2.nyi.mail.srv.osa ([10.202.2.161]) by compute5.internal (MEProxy); Tue, 29 Jan 2013 02:12:09 -0500 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:date:from:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; s=smtpout; bh=eQUfB2HXxb2PdHm1N74U7p EbPJM=; b=ZI5+TxZH0VN115uDGwRBmBDQz40BYdRhB4ad0Usn7ymOJR28Nf+Zn3 99ZwKoEYegG/9irx/qlzW/R77jTIo2oyXNm6wr8RWd2KRk+p+sC6LCTJ2LxDabYF 79LMN2HnQQmJ5uUZ7d2kal6m2p/Eb2popugygV0F9cklITSN0QRFA= X-Sasl-enc: ymt10ob3+G0a45EAa2ak5fJsXFEA9+Ev/Fay8ErbYRHk 1359443529 Received: from [192.168.42.21] (unknown [98.220.238.115]) by mail.messagingengine.com (Postfix) with ESMTPA id 779A348257F for ; Tue, 29 Jan 2013 02:12:09 -0500 (EST) Message-ID: <51077649.8010705@garfieldtech.com> Date: Tue, 29 Jan 2013 01:12:09 -0600 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2 MIME-Version: 1.0 To: internals@lists.php.net References: <76a9565b2a095a72063a68f106a6b457@mail.gmail.com> <5ed6711b24349c82b7c17dd450ff7c80@mail.gmail.com> <7165e8331e1070234771f7ae9573cdf8@mail.gmail.com> <5106690E.6040908@zerocue.com> <510679E0.1050603@zerocue.com> <510739F0.80602@rotorised.com> In-Reply-To: <510739F0.80602@rotorised.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Voting periods From: larry@garfieldtech.com (Larry Garfield) On 01/28/2013 08:54 PM, Ryan McCue wrote: > Zeev Suraski wrote: >> The vast majority of the PHP community is a silent one; These people >> don't participate here on internals; They don't attend conferences; They >> use it - the vast majority of them in a professional manner - and they >> picked it because they like it the way it is, not because of what it needs >> to become. For every person that subscribes to internals, there's a >> thousand (yes, a THOUSAND) people who don't (it's several thousands vs.~5 >> million). In fact, they're not completely silent. They speak in volumes >> - PHP 5.4 is used in less than 1% of the sites using PHP today, and even >> the relatively revolutionary 5.3 is still a lot less popular than 5.2. >> The new shiny features are not all that interesting for most people. > I'd like to speak to this as someone involved in WordPress development. > As a whole, despite being a huge project with large amounts of > developers and users, WordPress is pretty under-represented on > php-internals. > > One of the big reasons for that is that we're stuck with a lot of > backwards compatibility, both internal and external. We try hard to > ensure that our API to our plugins doesn't break, which unfortunately > has left us with being the go-to project for pointing out bad code. As > much as some may want us to, we're not going to go and rewrite WP in a > day to use new features, so internals discussions aren't that important > at the moment. > > We're also stuck with a huge number of hosts still on PHP 5.2: > http://wordpress.org/about/stats/ > > I'd say it's somewhat of a chicken-and-egg problem, in that WP can't > develop for what's not there, and hosts won't bother upgrading if they > don't have to. We only stopped supporting PHP 4.x when the usage dropped > below 10%, and I'd see the same occurring for 5.2. > Hi Ryan. While I understand that level of conservatism, I think it is somewhat unfounded. The PHP community at large decided to deprecate PHP 4 en masse, and put hosts on notice. It worked, too. The GoPHP5 project included over 100 projects and 200 hosts that collectively decided it was time to kill off PHP 4 and move to PHP 5.2. That launched before the PHP Internals team decided to deprecate PHP 4 [1] , and had been in the works for a few months prior. And that was even without the support of heavyweight Wordpress. If Wordpress announced that it was going to start requiring PHP 5.3 as of some date 6+ months in the future (and there are advantages to doing so that don't require major BC breaking rewrites), I think you'd see a rather significant abandonment of PHP 5.2 among hosts. Many other major projects already have. I would be rather surprised if Drupal 9 doesn't require PHP 5.4. (Drupal 8, currently in development, is very solidly PHP 5.3.) My point being, the chicken-and-egg problem IS resolvable. PHP userland developers do have that power if wielded correctly. We just need to wield it together. We shouldn't let ourselves be pushed around by cheapskate fly-by-night hosts again. Disclaimer: Yes, I was the lead organizer of GoPHP5, but not the sole supporter. [1] Internals started discussing killing off PHP 4 about a week after GoPHP5 launched back in 2007. Whether it was entirely coincidental or there was some causal relationship there is, I suppose, a mystery for the ages. --Larry Garfield