Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:92386
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain lsces.co.uk from 217.147.176.214 cause and error)
To: internals@lists.php.net
References: <CAKSD0w7JcGxcYrf7anZeGxGd4+U9BbSREnKfzW0eEpaoP0aWoQ@mail.gmail.com>
 <57136573.7070802@fleshgrinder.com> <57137F66.3080608@lsces.co.uk>
 <57138312.7020003@fleshgrinder.com> <57138848.70303@lsces.co.uk>
 <57138F9B.4030600@fleshgrinder.com>
Message-ID: <5713B289.5090600@lsces.co.uk>
Date: Sun, 17 Apr 2016 16:58:01 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101
 Thunderbird/38.5.0
MIME-Version: 1.0
In-Reply-To: <57138F9B.4030600@fleshgrinder.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Re: Improving PHP's type system
From: lester@lsces.co.uk (Lester Caine)

On 17/04/16 14:28, Fleshgrinder wrote:
> Most features that are currently discussed are aiming at enterprise
> applications that require more built-in functionality to ensure
> correctness, reduce the amount of tests (unit as well as runtime) to
> detect bugs, and where many developers work together at the same code
> base. Most features can increase agility and productiveness of such
> teams and allow them to implement new features and A/B tests faster. Of
> course many features require more knowledge about programming. This can
> also be bad for such teams because big teams almost always suffer from a
> huge knowledge gap. Despite that, it helps the more advance developers
> to create richer APIs that are harder to abuse and in turn allow the
> overall design to achieve previously mentioned goals.

And this is where the likes of Hack should be exactly where you are
working ... The vast majority of grass roots users don't need another
layer of complexity loaded on top of what IS a perfectly functional
platform. Adding types, complicating procedure calls and lumbering
everything with 'optional' layers of complexity is not something that a
small jobbing shop user has time to investigate the implications on his
client base. I'm still working through code that other have written and
trying to in many cases unravel exotic code that no longer fits the
modern programming style. I no longer take on any new clients as there
is enough work keeping my existing client base working, but there are a
LOT of people still using PHP5.2/3 who now need help if they are ever to
be brought forward.

Now if you were proposing something that actually validated the data
fully rather than some very restricted 'type' elements then it might be
worth the effort, but 'int' is only a very small part of validating a
number and we still need the rest of the validation library after you
install a replacement for that bit mf it ...

-- 
Lester Caine - G8HFL
-----------------------------
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk
Rainbow Digital Media - http://rainbowdigitalmedia.co.uk