Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:119914 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 76849 invoked from network); 11 Apr 2023 12:51:38 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 11 Apr 2023 12:51:38 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 34D1C1804F8 for ; Tue, 11 Apr 2023 05:51:37 -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=-2.1 required=5.0 tests=BAYES_00,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-ua1-f49.google.com (mail-ua1-f49.google.com [209.85.222.49]) (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 05:51:36 -0700 (PDT) Received: by mail-ua1-f49.google.com with SMTP id k20so5574690ual.2 for ; Tue, 11 Apr 2023 05:51:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; t=1681217496; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=kh9Cnoc3FWlS5UgNEuiPcmJ4nILfcMK7N1kmBtZcviA=; b=ljKDXrGRF0+42gXCgBJb7HU8GBA/xvcwluM5A7Td/+Zc7017amNh09OFBPljFFzGzM vUzYwCfeWYNxt6WyQA9pNuCrTZOl3e9C4H55p5VWv7WwOxaoAFAz2DN+h5LVK7SqizId MJWm77dXmnjH92wq8pAHIq3lT6elEVYt9T6jxiWD6v1n18/Q7ccNT6hosKRYtXAkUf6D bus6vy1c4fMNf7DnbUuBEh/oddNrsXkWCa4K/HuuRS6RDRS+NHXU1ELP2u5vu2ihJ2rr GPUP2rfFe/y1ZO5pW9JeBD3Y7FW48vEVkZTuiaeeEeirrQs1yu+EsvscD/bDx87Bd2fD q+GQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1681217496; 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=kh9Cnoc3FWlS5UgNEuiPcmJ4nILfcMK7N1kmBtZcviA=; b=zRNzYIsNbqN7Rzz/IZI6tAb4pO/eY8XC6qoy5Bs9EFyhy8zR8Qbo/AVRlMVaE+9iZu iHgjfAc+dvn1S12hB+wyZSHRtDq1PY1KG3ZJmFDiRI0RunyPpcd3xHO4jDFHuzYbH3au foeImq8IWZHSE76JTaeevnyqQxTxuOxmqtW1p527CA62DYxUn1Zx8D0SV5WGk5j/iKJq teKfMm/xidmSEFWkw0KiO9dhLtWqAVfi8FpZaJ0cOj3LIawiIMoeuS69BK2ZnvH5Kba5 yTn20UIgx3kfAUDlA6JavezVCa2WBX37jzIw4wsRsAU2QYgoqKlt6fpEJrFEbRrgpdjA GxBA== X-Gm-Message-State: AAQBX9eu3XAtT1+lBMKA5b2J5PVMtV8k7LxFHTA74vRi+y1hbwzkeFqG 4Kq6EHd848RyqTrLMybnXqheIn6VodUfvbE+0ys= X-Google-Smtp-Source: AKy350a+2Y8DoXG7GD9Mwr3IqMF/5o51O7MDaMocnu/BVWZnotdbVip0RGWNZhoZGSNAUyI5DAQQdQRHqMPRmdSwxLs= X-Received: by 2002:a9f:3153:0:b0:68b:817b:eec8 with SMTP id n19-20020a9f3153000000b0068b817beec8mr1580835uab.0.1681217495683; Tue, 11 Apr 2023 05:51:35 -0700 (PDT) MIME-Version: 1.0 References: <8abbed60-5569-4eca-ad12-957877feed9b@app.fastmail.com> In-Reply-To: Date: Tue, 11 Apr 2023 09:50:59 -0300 Message-ID: To: autaut03@gmail.com Cc: Larry Garfield , php internals Content-Type: multipart/alternative; boundary="0000000000009ed93205f90ef383" Subject: Re: [PHP-DEV] Future stability of PHP? From: deleugyn@gmail.com (Deleu) --0000000000009ed93205f90ef383 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Tue, Apr 11, 2023 at 5:40=E2=80=AFAM Alex Wells wro= te: > 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 wha= t >> you and I know today. >> > > I still do not understand why you're expecting the whole PHP project to > put in enormous efforts to keep the backwards compatibility and solve you= r > 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? > I don't *expect* the whole PHP project to do anything. Let me start by bringing up a quote: > [...] your thoughtful insight on how language changes [...] will help shape proposals in a much more significant way. Disclaimer: This quote is taken out of context, the original message can be found here: https://externals.io/message/110936#110937 As I've mentioned here before, I've seen a few folks bring up the message that I see on this quote as: Voting rights are not necessary to contribute to PHP Internals. PHP is an extremely large ecosystem and bringing community/user voices to internals can greatly help developers understand how the language is being used and how proposals can be shaped to help address concerns that are made aware. I'm not voicing my concerns in the hopes of making my problems your problems and that the PHP core developers should fix it for me. I have been going through a rewrite for the last 6 years and I expect to be done with it in the next 5. Every year we need to go back to the legacy spaghetti and upgrade it for security reasons. It's busywork and adds no real value to us. We still do it and we will keep doing it no matter what. But in the course of doing so, I lost coworkers to Typescript with a reasoning that it doesn't make sense to rewrite our product in a language that will keep breaking the codebase constantly. I'm not here to discuss the merits of their decision because if I 100% agreed with that decision, I wouldn't be here, I would be long gone and developing Typescript fulltime by now. But in my little bubble, losing highly talented PHP developers to Typescript has been a recurring situation and that loss of community members saddens me. So if you could please read my message as "here's what has happened in a small corner of the PHP community that is directly related to what OP has mentioned at the start of the thread (PHP stability). Maybe this is not new information to any of you here and there's nothing that can be improved on it unless someone drops 8 digits of money on the PHP project. Maybe that is a price that PHP has been willing to pay to keep on doing what it currently is doing. Or maybe there are some interesting things that can be taken into consideration. Do what you will with my participation. The only expectation I had when I joined this discussion was respect and that was almost completely met. --=20 Marco Deleu --0000000000009ed93205f90ef383--