Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:106527
MIME-Version: 1.0
References: <CAJHtznw0eKbBNJo9TnDwZvvbMMFt5mCo=+SpKLw0zYzq9tKWZA@mail.gmail.com>
 <5d4e9057.1c69fb81.bdf14.8d8fSMTPIN_ADDED_MISSING@mx.google.com>
In-Reply-To: <5d4e9057.1c69fb81.bdf14.8d8fSMTPIN_ADDED_MISSING@mx.google.com>
Date: Sat, 10 Aug 2019 11:04:09 -0400
Message-ID: <CACXBjuhfzX8vDXoJx2Q7EKQUu-2io=7+DyhCpWupt_8r15ijTg@mail.gmail.com>
To: Andrea Faulds <ajf@ajf.me>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000844d1a058fc49c89"
Subject: Re: [PHP-DEV] Re: P++: FAQ
From: rasmus@lerdorf.com (Rasmus Lerdorf)

--000000000000844d1a058fc49c89
Content-Type: text/plain; charset="UTF-8"

On Sat, Aug 10, 2019 at 5:37 AM Andrea Faulds <ajf@ajf.me> wrote:

> As the person who initially proposed and implemented strict_types, I
> think this is heading in the wrong direction. Perhaps that directive was
> a mistake, if it will lead to so many attempts inspired by it to
> fragment the language, including this one. Personally, I don't actually
> want a language like C++ or Java. PHP's flexibility is great, and I
> think splitting the language means going in a direction where you are
> forced to have everything be strict or nothing be. PHP++ sounds like
> Hack, but in mainline. I think it'll end up a mess in the long term.
>

Yes, I would suspect it would get a bit weird having a AnythingGoes
vs. NothingGoes barrier in the code like that. Forcing a balance, even
if sometimes the arguments get rather heated (and they were just as
heated, if not more so 20+ years ago), keeps everyone on the same
page and working on the same code-base without the us vs. them
situation that is bound to creep in.

-Rasmus

--000000000000844d1a058fc49c89--