Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:107031 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 1769 invoked from network); 13 Sep 2019 00:40:56 -0000 Received: from unknown (HELO php-smtp3.php.net) (208.43.231.12) by pb1.pair.com with SMTP; 13 Sep 2019 00:40:56 -0000 Received: from php-smtp3.php.net (localhost [127.0.0.1]) by php-smtp3.php.net (Postfix) with ESMTP id F26502D1FC4 for ; Thu, 12 Sep 2019 15:16:55 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp3.php.net X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_HELO_NONE autolearn=no autolearn_force=no version=3.4.2 X-Spam-ASN: AS3215 2.6.0.0/16 X-Spam-Virus: No Received: from mail-pg1-x535.google.com (mail-pg1-x535.google.com [IPv6:2607:f8b0:4864:20::535]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by php-smtp3.php.net (Postfix) with ESMTPS for ; Thu, 12 Sep 2019 15:16:55 -0700 (PDT) Received: by mail-pg1-x535.google.com with SMTP id i18so14168941pgl.11 for ; Thu, 12 Sep 2019 15:16:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=newclarity-net.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=ndjs0DEzqkqxKbtymNyhiUyTE1gajuo5Rkhn9BwiQt4=; b=cZdYSuQ5oGd6pg3fDRQ+MneDNMNE+DMWFMIaw/Dkvag12lqGCnwqXZubLzNwraGWe8 flEQI6kS2NmHSGsgQ2JF7twUkZZ5GCrMg7wn86n9bb5A2YMJkoczVJzJFTghFGwNUwV7 FJxYO8lWsA6tIIGesgfCU/ToPqHUR7RT10TfBZVuTp6hj6RT6gJUaasgSAKkUd8zags1 c786vXoTY/RjWVWh6nbxJv9d4gqW3NrNy/RxAGvMqtWbmru5y/MXCM4tzN9hJfFTOS4j D9M4Kw7vHd5/F4Awi3xCM/zme1FczxOJvhw+ktnfqaBJ9+/FTdfn15nXc7grEDNYUgwn Rc4w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=ndjs0DEzqkqxKbtymNyhiUyTE1gajuo5Rkhn9BwiQt4=; b=mq/RaLtceZfqKVtaAd7gHTyi6mlXHaweT1pMH2ZtjCzJ93FW62+v6Z6p5jMcSU156M 60JkLj04m/0W47XCphH47IHG0Kh6kKuY2+9Vu3I4jlGo106bslWakpbsrPaP+pBO67ut RNAvBIESqSa/YS0RkV2i8PUCUChnWZE9d2AZiOTIPXpqPq5ekC4y59yKHc9vmA0OmSMi EfvF16KpUW+s35lDIFvWscvEquRs2TNJQvp+QUa3mVfUL6a5jG37BMtqrAM7V8V/2vSQ qmnRHiB0Ug2VOeSYfOu3pCEE37r4l1Wb+rTktm1I+YSjaOHcIKiLbUVtKXK/G/CA+pKW vPiQ== X-Gm-Message-State: APjAAAV5UO8VtNzY2UriNkcd7/79JkjyFTK4SNhuG4kLFSTwgzslnVsH RJk50YXEIS+/tU5wIIxBHiuHVQ== X-Google-Smtp-Source: APXvYqw8WbC7+thiPmDkHgPN6N65BovTqFOpI5g6OxUjHbc05k9bJoca9nOshJ/1DUFysSQE7bwp6g== X-Received: by 2002:a63:1507:: with SMTP id v7mr38235315pgl.397.1568326614106; Thu, 12 Sep 2019 15:16:54 -0700 (PDT) Received: from [192.168.101.137] (50-252-183-45-static.hfc.comcastbusiness.net. [50.252.183.45]) by smtp.gmail.com with ESMTPSA id d10sm28677154pfh.8.2019.09.12.15.16.52 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 12 Sep 2019 15:16:53 -0700 (PDT) Message-ID: <77CA024D-3141-4707-8280-81CA78282AFA@newclarity.net> Content-Type: multipart/alternative; boundary="Apple-Mail=_CB904559-70D6-4C09-9A4C-DDDFF529E843" Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\)) Date: Thu, 12 Sep 2019 15:16:51 -0700 In-Reply-To: Cc: Peter Bowyer , PHP Internals List , Jordi Boggiano To: Lynn References: <076701d56978$86020910$92061b30$@php.net> <078e01d5697c$5512bc10$ff383430$@php.net> <31BD63BC-ACE0-4478-B241-E698D2D6F59C@newclarity.net> X-Mailer: Apple Mail (2.3445.104.11) X-Envelope-From: Subject: Re: [PHP-DEV] Changing fundamental language behaviors From: mike@newclarity.net (Mike Schinkel) --Apple-Mail=_CB904559-70D6-4C09-9A4C-DDDFF529E843 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 > How many of those are actually developers? Because the way I = understand this numbers, "powering the web", that doesn't mean 34% are = also developers. It wouldn't surprise me if a big portion of these = applications could've also be a system written in another language, = deployed, plugins installed, added some themes and done, no PHP = knowledge required. =20 Most WordPress users are *not* programmers. =20 Which is why introducing breaking changes to PHP will potentially affect = them so negatively; because they have no programmers on staff nor any = skill to fix the problem. Which means they will have to hire expensive = programmers =E2=80=94 like me!!! =E2=80=94 to fix a problem that from = their perspective they do not understand nor will even recognize a = benefit when the code is "fixed." Again, I am just presenting this perspective on this list. Those who = vote on this list will decide if breaking WordPress end-user's site = bothers them or not. -Mike P.S. I am writing during a break at a WordPress conference, ironically. --Apple-Mail=_CB904559-70D6-4C09-9A4C-DDDFF529E843--