Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:75335 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 22910 invoked from network); 8 Jul 2014 09:19:49 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 8 Jul 2014 09:19:49 -0000 Authentication-Results: pb1.pair.com smtp.mail=julienpauli@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=julienpauli@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.128.182 as permitted sender) X-PHP-List-Original-Sender: julienpauli@gmail.com X-Host-Fingerprint: 209.85.128.182 mail-ve0-f182.google.com Received: from [209.85.128.182] ([209.85.128.182:62713] helo=mail-ve0-f182.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 28/C0-19184-3B7BBB35 for ; Tue, 08 Jul 2014 05:19:47 -0400 Received: by mail-ve0-f182.google.com with SMTP id oy12so5468999veb.27 for ; Tue, 08 Jul 2014 02:19:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-type:content-transfer-encoding; bh=hgSavEf1GXH8T/y6M1syOg0Lgn3x8m+UdTMYypTvH88=; b=NkTIxSrKYYp2nKjqQ072HFL+g/T3RDZUvoZlROXV9dtwHZUWsng1knUuGj4qiZaUJQ mcvCOurd+agRzwfLv2nYhz2SKs1lvQDmi3bqMPo+BE5BkVEFc1E22xNztiwKA1U2GmbX UNU1sNjpZ3Rs3P69EmYxP+Hut4kGUbNh2nVme8PxNuDtAfaNdgbKxXBEbchnMAsuCnYp cfAxkmiQ8pZUNW/MNMgOe33NBhV3xY8t4OccP9u++fN0t4rWy27l50YiJ7HfgMEh+WcC lDOyzqeJSx22/XzSCYWqdbRCVAc72dNWtwc0t6L5taGTjZZGQbtTx3ATSgCW2uk4ydOh DjsQ== X-Received: by 10.220.190.197 with SMTP id dj5mr32709012vcb.19.1404811184021; Tue, 08 Jul 2014 02:19:44 -0700 (PDT) MIME-Version: 1.0 Sender: julienpauli@gmail.com Received: by 10.220.81.68 with HTTP; Tue, 8 Jul 2014 02:19:02 -0700 (PDT) In-Reply-To: <-3520606473386434774@unknownmsgid> References: <61EEC54E-7B8D-433E-A391-75F8D6A41E79@ajf.me> <650742796f119ed972a688a58e02242b@mail.gmail.com> <53BA8E93.8060708@lsces.co.uk> <1581132639526056444@unknownmsgid> <-3520606473386434774@unknownmsgid> Date: Tue, 8 Jul 2014 11:19:02 +0200 X-Google-Sender-Auth: bS3UabI_vH7ned2flarvohgC-ho Message-ID: To: Zeev Suraski Cc: Andrea Faulds , Pierre Joye , Lester Caine , PHP internals Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [PHP-DEV] [RFC] Name of Next Release of PHP From: jpauli@php.net (Julien Pauli) On Mon, Jul 7, 2014 at 3:13 PM, Zeev Suraski wrote: >> On 7 =D7=91=D7=99=D7=95=D7=9C 2014, at 08:59, Andrea Faulds = wrote: >> >> >>> On 7 Jul 2014, at 13:57, Zeev Suraski wrote: >>> >>> I don't think it's a problem, because I don't think we're two years >>> away from releasing a phpng-based version and I don't think it's a >>> moving target at this point. So I agree we need to remove these >>> uncertainties. >>> >>> I'm going to start an RFC-based discussion for moving phpng to master >>> so that the uncertainties around it are removed. >> >> phpng has mostly been just performance so far, right? Could we use this = opportunity, where it is not yet master, to make some deeper improvements? > > What do you mean by deeper improvements? > phpng is focused on performance. We can have other improvements for > the next version of PHP, of course... I'd like to start a discussion about IO multiplexing on that subject as well. We could improve lots of performance of both the engine and user scripts. I already started a topic about it on internals, and I should write an RFC about it. I'm also worried about the API of future PHP-Next. php-ng or not, I dont care. What I'd like is a clean API, and well documented, so that it is not as hard to get into code as nowadays. Nowadays its just very hard to put one's head into code when not familiar with it. I want for PHP-Next something clean and documented so that it will be even more open to new minds. Julien.P