Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:102391 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 3300 invoked from network); 24 Jun 2018 14:31:45 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 24 Jun 2018 14:31:45 -0000 Authentication-Results: pb1.pair.com smtp.mail=morrison.levi@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=levim@php.net; sender-id=unknown Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.208.178 as permitted sender) X-PHP-List-Original-Sender: morrison.levi@gmail.com X-Host-Fingerprint: 209.85.208.178 mail-lj1-f178.google.com Received: from [209.85.208.178] ([209.85.208.178:36123] helo=mail-lj1-f178.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 0F/89-13077-F4BAF2B5 for ; Sun, 24 Jun 2018 10:31:44 -0400 Received: by mail-lj1-f178.google.com with SMTP id o26-v6so4143626ljg.3 for ; Sun, 24 Jun 2018 07:31:43 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=DHdKF7XqQoT7Xt55lnX48+fqRCuOvFqQIrxILCa+abg=; b=GgFu378FIC3Z5udMc8DF2jIEeGH0e8Qn3Ens2cGwB1zhXx8napGZrgADQbjEuQjIVN nguXmhd6VTXyfFvJLdg0ceuGPDQMOQ9llGv/+Qpdap9067jj6s3D9KeRCd3Wxdh0bbaE SpstfEuI22pf4Qc2qdkzbp7KLRBzJP/Jj8lgbPw5LW97LgIt2CVCJ/vGPVvm3vFUUalq QU2zDMojxZh/e13JuIcqkcP07ekiLPpv0cr+NxGAN3dHWXe1OZUjoW1MuG8Lc4xPzogm DfAvMd0LmlBzHkGEWXygDzC7iibWSy06hcIphBuGv6YrcF254I6bjUwOc5yhrVhZVlv7 81Ag== X-Gm-Message-State: APt69E2mJ6/xGd+6fasfGMrS/ZNPHpqfm/bm/jNosCy6cdRI0Zt2Ap9D o01sZDRMtsbFczMl3NawSAW3xSzx+OUczQV9cRnPZPDU X-Google-Smtp-Source: ADUXVKJnZPUUMurFKcRd3SqycBmxkOKIgsMEWUjlkHLGOHodo51jhhahKIZLzL7M14XsMH/5SNH1SpLmLxVyrGn0Vzg= X-Received: by 2002:a2e:7d10:: with SMTP id y16-v6mr5204387ljc.29.1529850700224; Sun, 24 Jun 2018 07:31:40 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: Date: Sun, 24 Jun 2018 08:31:18 -0600 Message-ID: To: Zeev Suraski Cc: internals Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Subject: Re: [PHP-DEV] PHP 8 next? From: levim@php.net (Levi Morrison) On Sun, Jun 24, 2018 at 12:47 AM Zeev Suraski wrote: > > > Neither JIT nor FFI require backwards compatibility breaks in language.= I don't > > think either of those particular features would substantially break the= C API > > either. If these are the motivations for PHP 8 then I strongly object. > > Backwards compatibility breakages have never been the trigger for bumping= into a major release. They were *allowed* in case a major release was mad= e available - for different reasons. > > The trigger for a major release has always been very substantial improvem= ents/changes to the language, which I believe JIT, FFI and potentially asyn= c squarely fit into (and I'll explain why I think that separately later thi= s week). This is true for PHP 3, 4, 5 and 7 (even though 3 and 5 did intro= duce inherent compatibility breakages as a part of its new functionality). My position stands: I *strongly* object. If we rush to PHP 8 then it will be at least 4-5 more years before we have another chance for breakages in PHP 9. We can add features yearly.