Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:119843 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 64795 invoked from network); 9 Apr 2023 22:10:53 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 9 Apr 2023 22:10:53 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 6B41018037E for ; Sun, 9 Apr 2023 15:10:51 -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.0 required=5.0 tests=BAYES_20,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_ENVFROM_END_DIGIT, 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-yw1-f170.google.com (mail-yw1-f170.google.com [209.85.128.170]) (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 ; Sun, 9 Apr 2023 15:10:50 -0700 (PDT) Received: by mail-yw1-f170.google.com with SMTP id 00721157ae682-54ef6ca60ceso59867017b3.3 for ; Sun, 09 Apr 2023 15:10:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; t=1681078250; x=1683670250; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=uHRmiXgeNh3ZaCvdiQUjB1RMAAqlASzD1KkVpH0o4IU=; b=CNobP4xHOLuLnFkK9mRgELekti7v/rqZHPcgjkv3hdrjnyxugsOmJMTNBVFeGRt/84 4km6yQDSlXrYpcRTfRULKisq73zhK4T6pcYrBn5m+sPjBMIZAqwt2GNce1lv3jPuAeGh r9MGQ6VE67hoKis8FXzR3i/04IxHQVpBVRkIShnBHlfo4rQxjTCTEfawhIrDNXl1wp2+ PVjdkDVDftdQr6t7szhmZug1YOWgEE7WXoq+xYYCbM54vfwvIr2WF6p0ympx8nobw/ON 54O9UGBWt1QRCe2XFQXBlKxO2Jy0S2uCNcNvi/GG8r0bxMfntYSROptZQWTaNNaLE45X doIg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1681078250; x=1683670250; 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=uHRmiXgeNh3ZaCvdiQUjB1RMAAqlASzD1KkVpH0o4IU=; b=HFRxooZUjjefH2Hap/vLjeYrvlZP7bpy5vlQDQGQixNcETNwe6hFGJR5Vtx+fWVZe3 NSGCH91Ou86dUIjOsbO6RPPriZGtUfvajRVilszZZPhwhcBci1Qwwg0vGWzkh0f/UHJu wd6vCJmtu8jJM4C+432w6TWGR+6f3LOIssZ7cGBGlmkaDqdJ/PQuq9mafoPfeHQ0km+r EvEMRPw7g71MW6/sTErLDz/4m8+YHa8NgZbhhcxb8G53MYg0eKecyYzBv74/2PwwjmfG e+cwxXTRteE8H8DvhMGcKLhm6pYnS0nFm9niS+zy6o5DJ9+I0p1lFfdoyYZ1o6mYlgMp RR9Q== X-Gm-Message-State: AAQBX9f//CXAjJNhLNP1POUOfzwpsfSLBcXGIwwZ5kIMPLlL7fPUg4PO IQmu2KkKmyJ6iflb7sQIYzrRxhVF94dU5nvJrJg= X-Google-Smtp-Source: AKy350ZsggSiCY6Jr57BaIoqlHdOFrJQ1UQw0Q3HB2qkc50bamCXSHcP1/FTADLhCwYnH8uKIL35N+GgH5HNgI8VZxc= X-Received: by 2002:a81:aa14:0:b0:54f:2ad:91c5 with SMTP id i20-20020a81aa14000000b0054f02ad91c5mr1828193ywh.3.1681078250043; Sun, 09 Apr 2023 15:10:50 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: Date: Sun, 9 Apr 2023 23:10:38 +0100 Message-ID: To: Deleu Cc: Dan Liebner , Stephan Soller , PHP internals Content-Type: multipart/alternative; boundary="000000000000eefde105f8ee87c6" Subject: Re: [PHP-DEV] Future stability of PHP? From: tekiela246@gmail.com (Kamil Tekiela) --000000000000eefde105f8ee87c6 Content-Type: text/plain; charset="UTF-8" > But what's the point of starting a greenfield project in PHP while Typescript is right there? If that is true then we have pushed PHP to its death. PHP is dead and we can move on to other projects. But that's obviously not true. I could claim the complete opposite: why start a project in Typescript when PHP is there and it's a more mature language? At the end of the day, it comes down to personal preference. The language is perfectly suitable for greenfield implementation. If it wasn't, then there would be RFCs trying to change things that are wrong with it. > But the cost is catastrophic. If you have a legacy codebase hanging over your head you probably know how hard it is to upgrade it. I wonder about this every time I hear this claim. What exactly changed in PHP 8.0 that made the upgrade path so difficult? The upgrade to PHP 9 may be a little more difficult because of some of the recent deprecations, but that's still years ahead of us. So what's exactly driving people away from PHP 8? Why is the adoption dwindling? I'd rather say that the roadblocks people are facing in upgrading legacy projects are not specific to PHP 8, but rather a technical debt acquired over the past 10-15 years. Even if nothing would change in PHP 8, people would still complain about the upgrade because of unrelated reasons. But please prove me wrong. Is there actually any change in PHP 8.0 that is a major source of work? If PHP went in the wrong direction, let's suggest something to fix it. If there are no suggestions for improvement then what are people complaining about? Regards, Kamil --000000000000eefde105f8ee87c6--