Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:119943 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 41958 invoked from network); 11 Apr 2023 19:23:48 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 11 Apr 2023 19:23:48 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id C7A5318054A for ; Tue, 11 Apr 2023 12:23:47 -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-pf1-f172.google.com (mail-pf1-f172.google.com [209.85.210.172]) (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 12:23:47 -0700 (PDT) Received: by mail-pf1-f172.google.com with SMTP id d2e1a72fcca58-63243b0e860so762968b3a.2 for ; Tue, 11 Apr 2023 12:23:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; t=1681241026; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=vlp2mnWSGjD3mxcwL9o8FhGpqAO2uh1eLGXcMU/cIIU=; b=J6rCkYZQaAq0cle9y3XpzgXrq2iOuhSmnfSfHboZlZRjtt/yDcE8vTTMF6m6Pc5YLt g8g0a0XybG6zTkxqJ/LGH/QvexhbveLSWK0Jug9Xlugg0eRInHYBSFQ7ABaBT3IP9IBs kVqz7nJXd41cHC1OsjnFkJwR8VboMiQi8St+DzZFbTUJtOObrBlOBpi5f+3HFWoG5BGL 0TM+TS7JKdMMZkvY4QnYjDEO3eyADFKav3Qn6g7xoS1gb6L9bys/0LQ5dyStcRbOnQ5Y /YDI84mVe+RWa1ig1t28xkJHx+aa/BpaL2fRFpucJon7JH3T85XD69DMUToPA8INZZr3 7Ujg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1681241026; 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=vlp2mnWSGjD3mxcwL9o8FhGpqAO2uh1eLGXcMU/cIIU=; b=o68qJCCzzhN9Wub/Yf+EUIt6kvpDTo9/tg4ZX9T1WU7Nhl0yNwyLE54BpMNs19E6Wv bNUeoYXo4M96GE5rtZWQCNBDT3pGUyL17PVmhbGupL2drU39SJbBEjw2wDrOBimp/uTN dxI9r/ngROetH8ItUGsSOTyH7QIcyQubAqxPqh5EVGZujea9W+40nHAasYN0/NJdC7vT 0Z3A/oIRDLCviOX+DnFWmK2cl3q85gpzuwcwqkxueVqVVztPd6pfF1lsAlotCSI74f2Q e2ZJmhKfr1pbuCgDXq1Bp6MYF/Xz5eNmgnJ85cWLoY5ZNZg6e46goUGDqJeTDWzHK65+ K2WQ== X-Gm-Message-State: AAQBX9csEclvdMLEGakZ5mb21aVQZPmObJxlj3UdihtRa4yulTRaaE4a rRAFgct0gg3rDEW19nLvjCb3pCGSDkRQ74O6onA7b+pjNyc= X-Google-Smtp-Source: AKy350bx0gk81GXP3uGX+xniupQd5SFhEscjkGr663nwuAo0w2N5J4cEK54CKxM2XT/YCCaqWUdIFo3Va/M5vxbJt8M= X-Received: by 2002:a05:6a00:2d04:b0:62b:f8e9:2a17 with SMTP id fa4-20020a056a002d0400b0062bf8e92a17mr7130076pfb.3.1681241026004; Tue, 11 Apr 2023 12:23:46 -0700 (PDT) MIME-Version: 1.0 References: <8e290ea0-88b5-8730-98de-2eca56171b16@gunnard.org> In-Reply-To: <8e290ea0-88b5-8730-98de-2eca56171b16@gunnard.org> Date: Tue, 11 Apr 2023 22:23:33 +0300 Message-ID: To: Gunnard engebreth Cc: PHP internals Content-Type: multipart/alternative; boundary="000000000000230c6905f9146e80" Subject: Re: [PHP-DEV] Future stability of PHP? From: arvids.godjuks@gmail.com (Arvids Godjuks) --000000000000230c6905f9146e80 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Tue, Apr 11, 2023, 22:14 Gunnard engebreth wrote: > > On 4/11/23 3:09 PM, =F0=9F=98=89 Good Guy =F0=9F=98=89 wrote: > > On 08/04/2023 19:36, Stephan Soller wrote: > >> > >> > >> A few days ago I migrated a project from PHP 7.1 to 8.2 and the > >> amount of > >> deprecations and fatal errors spooked me a bit (details below if you'r= e > >> interested). That got me wondering about the long-term stability of > >> PHP (as in > >> language and API breaks) and I looked at the RFCs. I got the > >> impression that > >> static typing has a lot of traction now and I have no idea of what > >> the fallout > >> might be of changing a dynamically typed language into a statically > >> typed one. > >> Also API breaks seem to become more frequent (e.g. utf8_decode). I > >> stumbled > >> across the language evolution RFC proposals but it seems that > >> approach was > >> abandoned. > > > > I think the php focus has shifted from its original ethos. PHP was > > designed to be a tool to access sql databases and so the language was > > quite simple. > > > > Now php has become so difficult that people are asking what is the > > point pf PHP when programming languages such as c# or C or C++ or JS > > can do everything. It is difficult to learn these languages but so is > > PHP because it is becoming more like a desktop programming language. > > Might as well spend time learning main stream programming languages. > > > > PHP should focus on one thing and one thing only and that is to be the > > simplest tool for sql servers, mainly MySQL but also try supporting > > MS-SQL and PL-SQL (Oracle's premium database system). > > > I think this thread's focus has shifted from its original ethos... > > i'll see myself out ;) > Touch=C3=A9. This was just too classy of them not to acknowledge. --000000000000230c6905f9146e80--