Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:101596
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.52 as permitted sender)
To: internals@lists.php.net
References: <CAEUnE0d+rHG-Rvjt7QAN6x6L+BP5Yb_cz8sGuOFDOkx-kCehkA@mail.gmail.com>
 <9a3a8760-f65a-a5c0-b318-1830a9a986c3@gmail.com>
 <CAH0Uv3H_DEPZ5HmaKGe08_DMrzndBz7ofJTUgeb4f66zeaj1EA@mail.gmail.com>
 <9352F6DF-9940-49A2-9B1D-FA9258E9738E@lerdorf.com>
 <bb4579ba-2e09-4199-a871-be4428a1ee2d@lsces.co.uk>
 <ee3d2ffc-a72c-78f3-281b-dd029c706105@gmail.com>
 <CAEUnE0eShfm4kZck=2gBef6cgU6DdrKggtotUK+Jyk6uPYOYFg@mail.gmail.com>
 <CACXBjugZrXXORVsaFhJzRO_WEiUXnVEHBBuHZysPUGRN6Ls7nw@mail.gmail.com>
 <CAEUnE0ce2HRfsKOy_=NSnrENUnGpB4m-C=cMQFV93MgbaMguOQ@mail.gmail.com>
 <CACXBjuij=ZeL-upuwNrEWuSxB9PKjVXWwfwRCBReVzUi_eQBUw@mail.gmail.com>
 <CAEUnE0dAO2UAcGhc2jwWkjF8gh624j3ouVnitYSM-JCsvN176w@mail.gmail.com>
Message-ID: <49eeb31e-a548-6682-379b-5c923159e0c4@gmail.com>
Date: Wed, 10 Jan 2018 21:08:38 +0000
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101
 Thunderbird/52.5.2
MIME-Version: 1.0
In-Reply-To: <CAEUnE0dAO2UAcGhc2jwWkjF8gh624j3ouVnitYSM-JCsvN176w@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-GB
Subject: Re: [PHP-DEV] [RFC][DISCUSSION] Strong Typing Syntax
From: rowan.collins@gmail.com (Rowan Collins)

On 10/01/2018 18:39, Michael Morris wrote:
> On Wed, Jan 10, 2018 at 9:04 AM, Rasmus Lerdorf <rasmus@lerdorf.com> wrote:
>
>> Describing the syntax/UI for a feature like this is nothing like the
>> architectural drawings for a skyscraper.
> In terms of time and effort spent it is. It often takes years to complete
> plans drawn up over the span of weeks. The analogy becomes more firm when
> you compare the man hours on each side - an architect can draw up plans for
> a house in less than 100 hours (unless it's a freaking huge house).

I don't think Rasmus was saying architects' plans aren't important, or 
making any comment about the scale of the task. I think he was saying 
that things like syntax and UI are not the appropriate part of the 
process to compare to architects' plans. Architects know how buildings 
work, and spend those weeks making sure the subsequent years aren't 
going to be wasted because the plausible-looking shape the client asked 
for can't actually support its own weight.

And just to be clear, this particular feature IS a freaking huge house. 
Worse, it's a type of skyscraper nobody has ever tried to build before. 
Sketching the kinds of shapes it might have is interesting; getting hung 
up on what size the windows are (the exact keywords to use) is probably 
a waste of time until we've figured out if there's a material that bends 
that way. And saying "hey, could you make it out of carbon nanotubes?" 
is a fun conversation to have over a beer, but probably isn't going to 
be that helpful to people who are experts on skyscrapers and material 
science.

Apologies for extending the metaphor somewhat beyond stretching point, 
but I think it acts as a reasonable illustration of where people are 
coming from in this thread.


> Plans still must precede work, and if the ramifications of those plans are
> to be far reaching they need to be agreed upon as early as possible.

Absolutely, and unfortunately, the biggest ramifications of this 
particular type of change is going to be in the very core of the engine. 
That's not true of every feature, but for this particular feature, one 
of the parts that needs planning and agreeing as early as possible is 
"how are we going to do this without killing performance".


Regards,

-- 
Rowan Collins
[IMSoP]