Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:84877
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.217.176 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAFMT4NqHW0acXGwKJVDR9P92GQnR1AoGp9Pb4n3j3Dtvw6X+yA@mail.gmail.com>
References: <CAAyV7nEikYZNmaAnRy9hkRBnDDP=Ey43-nZbJGMHmQ_dAC_vgw@mail.gmail.com>
 <5505C875.1030202@gmail.com> <CAL0xaBF_HLP7pe64OxbNofDpKWxnJ3MMakjLMzUAA78oq7r2yQ@mail.gmail.com>
 <CAFMT4NqHW0acXGwKJVDR9P92GQnR1AoGp9Pb4n3j3Dtvw6X+yA@mail.gmail.com>
Date: Sun, 15 Mar 2015 21:15:14 +0200
Message-ID: <CAL0xaBErv15xczFA-Gnzfgr3Ew-vnKyMBpU55Bs702FZefPEYA@mail.gmail.com>
To: Levi Morrison <levim@php.net>
Cc: Rowan Collins <rowan.collins@gmail.com>, PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=047d7b3a82ded020a10511588ed0
Subject: Re: [PHP-DEV] Voting irregularities
From: arvids.godjuks@gmail.com (Arvids Godjuks)

--047d7b3a82ded020a10511588ed0
Content-Type: text/plain; charset=UTF-8

2015-03-15 20:55 GMT+02:00 Levi Morrison <levim@php.net>:

> > What we need, is a MANAGER! To manage the Type Hint development. And one
> > that is not doing real development on PHP core, but someone with
> > understanding.
>
> You are basically saying we should hand development of a critical
> language feature over to someone not doing real development on the
> language. I don't see how that could possibly end well.
>
I'm saying you need a manager to orginize the process, and as I see it,
make it a multi-version effort, like the OOP has evolved. Well, I probably
over-generalized. It has to be atleast a userland developer with good
amount of PHP development experiense under his/her belt to understand, he
needs to have patiense, and above all, he needs to discipline himself on
amount of writing and replying, otherwise it will get messy again. It can
be a core dev too, it's just from what I have seen, people push their own
agenda too much when they are the developer behind the RFC. It's good over
all, but I think this paticular case is an exception.

And based on how long the type hints are taking to get anywhere, I say it
needs some special handling.

Type hints mutated over time from a simple proposal into something big,
over-engeneered and over-agressive. I have never seen a feature so complex
being done in a single go into PHP since i'm folowing internals list, and
that's since late days of PHP4...

So, long story short: I suggest we restructure the effort and have someone
impartial at the helm mediating the work being done, draw some lines and
execute a plan people can agreee on.

--047d7b3a82ded020a10511588ed0--