Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:52318 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 88716 invoked from network); 11 May 2011 19:17:50 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 11 May 2011 19:17:50 -0000 Authentication-Results: pb1.pair.com smtp.mail=dukeofgaming@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=dukeofgaming@gmail.com; sender-id=pass; domainkeys=bad Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.213.42 as permitted sender) DomainKey-Status: bad X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01 X-PHP-List-Original-Sender: dukeofgaming@gmail.com X-Host-Fingerprint: 209.85.213.42 mail-yw0-f42.google.com Received: from [209.85.213.42] ([209.85.213.42:55057] helo=mail-yw0-f42.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 87/92-10064-DD0EACD4 for ; Wed, 11 May 2011 15:17:50 -0400 Received: by ywh1 with SMTP id 1so338807ywh.29 for ; Wed, 11 May 2011 12:17:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=5cSPzayF3te8Q485as2thDpwvXX5vTZ7sNQbFwK+dck=; b=NU5bGNn1Rb+M4l0maxZ6A9iKvLox7yc/MnO7cJ6MgBHjVqC3XoQiTVZkSEYtZvrC9e bs5rFND1GmjkYGdHPBFzO8WywfH9Ng70oNKfizU0Oyfy7HJ/a6HZ2hf9qjMS7hQBwRSl DXaJvwH2qkjt22rte3e3kel3bA+VULH1nr1T0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; b=Bs1XcZIuUXZKhN2ezgwa/YRoNYs7k4nlBmoQTSvfWFKgMJmh2/VDfYkZoKFh4wSByy QPNBrqL2o9LdfVMz/aDJyeKwu8Jkuzqhd+zLawu2iCVWcqwXCYrrY5o9KVf2aTeBXIHF MGrq374NTIZ53NlDq/2Cx1c2E1Q1LgEVECMV4= Received: by 10.101.185.34 with SMTP id m34mr5840335anp.83.1305141467246; Wed, 11 May 2011 12:17:47 -0700 (PDT) MIME-Version: 1.0 Received: by 10.100.108.6 with HTTP; Wed, 11 May 2011 12:17:27 -0700 (PDT) In-Reply-To: <4DCAC067.5030801@lerdorf.com> References: <4DC729EE.9090600@sugarcrm.com> <4DC75FFF.40008@lerdorf.com> <4DC7A7F0.4000504@sugarcrm.com> <4DC819D0.5010008@lerdorf.com> <4DC81ED6.1050902@sugarcrm.com> <8757232E56758B42B2EE4F9D2CA019C9013F9F59@US-EX2.zend.net> <4DCA2192.4080201@lsces.co.uk> <4DCA5744.1030907@lerdorf.com> <4DCAC067.5030801@lerdorf.com> Date: Wed, 11 May 2011 14:17:27 -0500 Message-ID: To: Rasmus Lerdorf Cc: "guilhermeblanco@gmail.com" , PHP internals Content-Type: multipart/alternative; boundary=001636c5bba089720004a304ed2e Subject: Re: [PHP-DEV] annotations again From: dukeofgaming@gmail.com (dukeofgaming) --001636c5bba089720004a304ed2e Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On Wed, May 11, 2011 at 11:59 AM, Rasmus Lerdorf wrote= : > > > My main concern is the trickle-down effect a major low-level engine > addition causes. Your patch is just the tip of the iceberg which will cau= se > dozens of people weeks of work to account for the new code all across the > PHP ecosystem. The most complicated being the opcode cache support which > really only can be written by a handful of people due to the complexity > involved. Combine that with the fact that other projects who currently us= e > annotations, perhaps not to the level of Doctrine, but still, state that > they would have a hard time switching to this new approach it becomes rea= lly > hard to commit all these people and all this time to this. > > We are severely resource-constrained when it comes to people who can writ= e > solid low-level C code and we have to be very careful what we ask our > volunteers to spend their time on. A volunteer developer who isn't excite= d > about a feature is going to drag her feet and it will sit solidly at the > bottom of the priority list for months, if not years. If a key piece of t= he > eco-system isn't updated because of this one addition, it means that > potential PHP 5.4 users may have to wait 6, 12, 18 months before they can > migrate to the new version. > > Therefore, low-level engine changes, syntax additions, or entirely new > grammars as is the case here, face an uphill battle. If there is a way to > currently solve the problem without major changes, even if it is an 80% > solution that will weigh heavily against accepting the new code. > > Without broad support and enthusiasm, especially from the people who have > historically been the ones that write the code and track down and fix the > bugs, low-level features like this are doomed, no matter how > well-intentioned they are. That explanation sheds a lot of light on the general situation, thanks. Something I wanted to ask =97regarding resources=97 is, is GSOC being lever= aged this year in any way?. I'm guessing there could be lots of enthusiasm packe= d there, perhanos not that much for C writing, but for clearing the way for C writers. --001636c5bba089720004a304ed2e--