| From: |
| Rasmus Lerdorf <rasmus-AT-lerdorf.com> |
| To: |
| Andrea Faulds <ajf-AT-ajf.me> |
| Subject: |
| Re: [PHP-DEV] Re: P++: FAQ |
| Date: |
| Sat, 10 Aug 2019 11:04:09 -0400 |
| Message-ID: |
| <CACXBjuhfzX8vDXoJx2Q7EKQUu-2io=7+DyhCpWupt_8r15ijTg@mail.gmail.com> |
| Cc: |
| PHP internals <internals-AT-lists.php.net> |
| Archive-link: |
| Article |
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
