Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:107061 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 53862 invoked from network); 13 Sep 2019 11:23:48 -0000 Received: from unknown (HELO php-smtp3.php.net) (208.43.231.12) by pb1.pair.com with SMTP; 13 Sep 2019 11:23:48 -0000 Received: from php-smtp3.php.net (localhost [127.0.0.1]) by php-smtp3.php.net (Postfix) with ESMTP id 0EF3E2C6C38 for ; Fri, 13 Sep 2019 01:59: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=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,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-ot1-x335.google.com (mail-ot1-x335.google.com [IPv6:2607:f8b0:4864:20::335]) (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 ; Fri, 13 Sep 2019 01:59:54 -0700 (PDT) Received: by mail-ot1-x335.google.com with SMTP id g25so27508961otl.0 for ; Fri, 13 Sep 2019 01:59:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=L2ABI3v+P6ZsSIdoKS2Xq5GsXssG8td8FFasfPSy1v0=; b=LfX/qSOagjJDD2YQIGDuBuIPcUsADn5ExikLiW2ttCZUmvrsYxjQrNT2Xk8w0cgPP0 Q04Y2upi60EKAEVPf1cJjeDZfQSoKGd9YwXDdsgvT2jCt12q/17Smx9KgmIyjulABGyB sTIl0YO8Xm59wDCkWtx5ym0dfCTFPiXAdvbYbR6pBp5S4XqICDNM79QrP2ntvVTmB7pp QsRNbIilx0bnJNMURWjK+se1BjAtaBvpCbE0mhRwz1jnRiN377iwerJdKm9MP36LiiGe RUSvHGaSsajxH0mSDBBhgVRDUiI3a//kmo5iEAfUTOK5gYoDH5OsW79VR4WjkOM2eC2D XbuA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=L2ABI3v+P6ZsSIdoKS2Xq5GsXssG8td8FFasfPSy1v0=; b=VoUdTwmgTcoV35++YTJi+YrFoYrE+hpsEQMyI8DVLP7101Y6t1/39SD9v8C9D6Jb+U GRVOi9nVOxDfQb1R0K83AX49EcVIKPlkZ1WVSyIkSBbo6kovJmNr/TljOAe0TIqBOCBL QMAs5RiMstQaoxN1QdcLTD+3LApfoqvU8iKo3/CGi/HIwWO93x5KcWpPdxXYtSGo0ix1 44dl0qHFyu5Zzh5EYLgupIHQIlr1bXGllX0Ztc0XWAXjcpi4e5ggdwV6XOmGSM0N1a7I meyd/xGIokTyjXnXC/XTudv22GEM4I0cl19l3jbu+6hTv+ViaZzWtezA0xSUlu+rnD1n SxqQ== X-Gm-Message-State: APjAAAUHS2K5mv3ykDssc38p6CNZTZUdM5kVyBuZeH9a8T8ngNxABgl2 puBGtvrnwEhHHd4QFaF20Uyxg0Ggl8tMeNkgQmQmiqP8 X-Google-Smtp-Source: APXvYqy8tDl5YnH9q868KTgEbIDQLPNBpOmX+WjOmH8L/QtS+hGcrdYTnT397lBadQcwYZaGWpS0SHK7Ox1g1FqBrCA= X-Received: by 2002:a9d:148:: with SMTP id 66mr9967777otu.1.1568365194198; Fri, 13 Sep 2019 01:59:54 -0700 (PDT) MIME-Version: 1.0 References: <076701d56978$86020910$92061b30$@php.net> <078e01d5697c$5512bc10$ff383430$@php.net> <31BD63BC-ACE0-4478-B241-E698D2D6F59C@newclarity.net> <16AF0744-80CF-4245-B8F7-2A841C2461E1@newclarity.net> In-Reply-To: Date: Fri, 13 Sep 2019 09:59:33 +0100 Message-ID: To: Robert Korulczyk Cc: Mike Schinkel , Chase Peeler , PHP Internals List Content-Type: multipart/alternative; boundary="00000000000047426705926b7a25" X-Envelope-From: Subject: Re: [PHP-DEV] Changing fundamental language behaviors From: oludonsexy@gmail.com (Olumide Samson) --00000000000047426705926b7a25 Content-Type: text/plain; charset="UTF-8" I'm thinking this thread is receiving much attention than really required. Irrespective of the left and right argument, I think everyone wants a better language, the leftist are just arguing on a very lazy fact, not that they don't see anything bad in their wrong argument they are all just trying to hide behind "We know it is bad or can be devastating, let's just leave it as it is and hope nobody ever have reasons to clean it since it is still working" but me and those rightist are all like, this is wrong let's save billions of codes that could still be added to this buggy behavior than leaving it and hoping it would be one of the best dynamism people want from PHP. How does bug translate to dynamism? Why were there notices if something wasn't wrong somewhere with the behavior? If I'm to argue as php-src(being human), I would never allow those leftist to use me to write code again coz it is highly straining to pretend to know what an undefined variable meant( to be an int or string, or even an object) or even if it was a typo. We are straining the language performance even more by making it guess what the undefined variable would have been. Even a string would still go up as integer the moment you add ++($i++) to it. Why don't you people see it is safe and would be in everyone's best interests if we could clean this garbage behavior once and for all to live peacefully, and possibly reduce the amount of baggage behavior lying around in millions of codes out there, coz the counts increase every single day because everyone thinks it is the right behavior yet their error_log keep on getting notices? Zeev said the RFC was never meant to deprecate things and as such the voting would eventually not pass on to implementation even if it was accepted - "why then do you vote no on the RFC if it was never a valid vote to count?" I think voting on the RFC validates the RFC for all you've voted it for which means it's a valid way to deprecate features, else all formerly deprecated features can be reverted since they are invalidated by the current situation(or eye opening statement you just made). I think we all need to see from the right spot how many people and code we would save if this garbage were reported as Warning or error as early as possible than waiting for never yet still giving me notice in my error_log everytime PHP hit an undefined variable. One thing some people are forgetting is that this is an open source community and people(myself included) coming here to pull, push, commit, test, manage and even join the mailing list are not getting paid by anyone to do so(there might be an exception), and being an open source project we all need to agree to disagree no one has any authority over anyone. If there's been some laid out rules about some chairmen and the authorities they posses to always swing things in their favor, I'm very sure this project would have been dead on arrival( while there are so many projects wanting attention), since a open source project needs help from contributors I think we all need to think properly about rules or guidelines that might hurt the project's contribution. I don't pray to see PHP 9 timelines not posted by anyone(coz there's no one around to do so) or even php-src to be one of those languages where their contribution reduced drastically based on some people's bad influence affecting the other contributors. Let's argue rightly and expect other people to not agree with us, that's the default. Thanks, Samson(noobshow) On Fri, Sep 13, 2019, 9:11 AM Robert Korulczyk wrote: > > Upgrading the ~68,000 open source plugins available on wordpress.org < > http://wordpress.org/>, thousands of commercial plugins, and and an > untold number of custom-developed bespoke plugins and custom themes is > where the concern lies. > > Many of these are ticking bombs - unmaintained extensions with possible > security issues. Right now the biggest problem of WordPress ecosystem is > quality of community extensions and themes. Cutting of all old and > unmaintained extensions may be not that bad... > > > Regards, > Robert Korulczyk > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > > --00000000000047426705926b7a25--