Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:119901 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 48432 invoked from network); 11 Apr 2023 08:56:23 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 11 Apr 2023 08:56:23 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 65C651804D5 for ; Tue, 11 Apr 2023 01:56:22 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp4.php.net X-Spam-Level: X-Spam-Status: No, score=-0.7 required=5.0 tests=BAYES_05,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM,HTML_MESSAGE, RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_PASS, T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.2 X-Spam-ASN: AS15169 209.85.128.0/17 X-Spam-Virus: No X-Envelope-From: Received: from mail-ej1-f44.google.com (mail-ej1-f44.google.com [209.85.218.44]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Tue, 11 Apr 2023 01:56:21 -0700 (PDT) Received: by mail-ej1-f44.google.com with SMTP id dm2so18570580ejc.8 for ; Tue, 11 Apr 2023 01:56:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; t=1681203380; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=enoShtN/vK/fN5cJZBJPuU0G9RqwAx6aaKpCJ1mvCho=; b=n2ONgcD+dt6uC2yqhKnlvalN9qolxOtqqYBZ4kw+SoQ6svrs6K+zBKPy5i/mRF/ZN7 itL4IEWAQARrL2j19bUdV4BwxGl98ADNxSEwWccGsXQJSHbxjI8gp6xG2QDapEmsoZCh K62yY+xO7FgWAJ13b6f6nJmQXzFxDPCGJQYAPe0Qh2JOElFTHVNJDfQcc7CoaitycH9P E36WC0nMZH3n6xxd9zhdkkEJFiCRPnoXtScJ05nmVPXBPq9KX4/b93wL6xy9YCxEluWl GfixlQPXylq0YIL4Ib6yGsSs4xW1i6xAy7MuzxRhibEpe+w0NovdCfIy3PSHzOy7Jx2M Gavw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1681203380; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=enoShtN/vK/fN5cJZBJPuU0G9RqwAx6aaKpCJ1mvCho=; b=Zsi0EgcooaD9Di5lweDkIk2gRBieDgr61s4QEZeN/jw5TAHcupIsgDL5f8RpxauNqa fhNR/DjpgUch7fohT12YEVDZPrR5+k96trg3f3C5OWuzun/LORllu7aNEXgqNVS27fKp KfjnIDCz/M4Mdqb38rzY/T7kc1TK4vCxfrQAuiHr1tjxFsxR9KBgYujvTRGeqS6kHUo7 Cg3XC0Dfif4y3g7M/MODtTNnWV6ftm52Nuzej+46wRdRLBVULR2aXFwmOZPBPcI2C0O/ bJo8TuXDgLsB1AHLBAfzXUgz00wPIq30geTXRXdG8E8hSIY6FrMhmR1ASe7eYvOgs5LG cssQ== X-Gm-Message-State: AAQBX9d9yo5SSK/FRlCb99Je76GuAaCua4Flp36ab3DDhh9lwf6Lpx/v ZxvoS2aQEW6WSzNkzxAsrS871paqxsZITubMQvCcHauKMKk= X-Google-Smtp-Source: AKy350Z6i3t1/tYNunk9BKMmRCgTiPJtIYLI/jeoyhsqUx1jmUY/jWeM/eYRrnJIveS6rsN648HUEimvJRcMdWj1S3k= X-Received: by 2002:a17:906:830c:b0:94a:7c21:6ade with SMTP id j12-20020a170906830c00b0094a7c216ademr2934598ejx.5.1681203379928; Tue, 11 Apr 2023 01:56:19 -0700 (PDT) MIME-Version: 1.0 References: <8abbed60-5569-4eca-ad12-957877feed9b@app.fastmail.com> In-Reply-To: Date: Tue, 11 Apr 2023 10:56:08 +0200 Message-ID: To: autaut03@gmail.com Cc: Deleu , Larry Garfield , php internals Content-Type: multipart/alternative; boundary="00000000000041821505f90baaba" Subject: Re: [PHP-DEV] Future stability of PHP? From: ocramius@gmail.com (Marco Pivetta) --00000000000041821505f90baaba Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable I'm also curious to hear whether any participants in this thread do/did support the PHP foundation in any tangible way :D If you treat it like an LTS provider, perhaps it's time to pay up the LTS support fees? Marco Pivetta https://mastodon.social/@ocramius https://ocramius.github.io/ On Tue, 11 Apr 2023 at 10:40, Alex Wells wrote: > On Tue, Apr 11, 2023 at 6:10=E2=80=AFAM Deleu wrote: > > > I don't want to use those weird stuff, but I'm > > doing the best I can to replace every single line of old code that has > been > > written in an era that "best practices for PHP development" were not wh= at > > you and I know today. > > > > I still do not understand why you're expecting the whole PHP project to p= ut > in enormous efforts to keep the backwards compatibility and solve your > problems (temporarily) instead of you doing so. What's stopping you from > using the last supported PHP version by that codebase and fixing or, wors= t > case scenario, rewriting it if you wish, while on that (non latest) PHP > version? What causes the desperation to update to the latest PHP? Is it n= ew > features or security fixes, or both? > --00000000000041821505f90baaba--