Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:78705
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.192.47 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <5457D749.2010406@gmail.com>
References: <002601cff777$eb923430$c2b69c90$@tutteli.ch>
	<68518A5F-4A11-4D93-914D-760A4CB447E8@ajf.me>
	<5457D749.2010406@gmail.com>
Date: Wed, 5 Nov 2014 12:47:55 +0700
Message-ID: <CAEZPtU6ke4m38cnmZDGr11C==be4KDAx3nVtPu8wY_krnX6xBw@mail.gmail.com>
To: Stas Malyshev <smalyshev@gmail.com>
Cc: PHP internals <internals@lists.php.net>, Robert Stoll <php@tutteli.ch>, Andrea Faulds <ajf@ajf.me>
Content-Type: multipart/alternative; boundary=001a11c12aa615f4f80507161fe8
Subject: Re: [PHP-DEV] Types on the right or on the left
From: pierre.php@gmail.com (Pierre Joye)

--001a11c12aa615f4f80507161fe8
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Nov 4, 2014 5:28 AM, "Stas Malyshev" <smalyshev@gmail.com> wrote:
>
> Hi!
>
> > PHP doesn=E2=80=99t need more inconsistency, sure, but we must be pract=
ical
> > here. It is bad if PHP and Hack have the same feature with different
> > syntax, it will cause developer confusion and further segment the
> > communities.
>
> Given that Hack is a different language, which was designed AFAIK with
> little input from PHP community, I don't see how there would be any
> confusion - it's like saying PHP and Perl or PHP and Java having
> different syntaxes leads to segmenting the communities. In fact, there
> are two different communities - though, of course, people can belong to
> both - and two different languages. I do not think Hack syntax should
> have much weight in decisions about what syntax to choose in PHP - it's
> a different language, even though it has many similarities.

I have to agree with you here.

Hack did not ask us for any of the specific things they did, whether we
plan to do it, propose RFCs to get consistent syntax and behaviors for both
projects.

I tend to think it was on purpose and we should not base our decisions on
hack. That does not mean we cannot map one feature or another but let stay
independent, they can change that for any future changes if they wish
consistencies between the two projects.

--001a11c12aa615f4f80507161fe8--