Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:91610
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.217.173 as permitted sender)
MIME-Version: 1.0
References: <1F.91.55238.41F10D65@pb1.pair.com> <FA.10.10408.29514D65@pb1.pair.com>
 <56D42CD3.6020602@gmail.com> <DB.E1.07778.3D165D65@pb1.pair.com>
 <56D57DF4.8000906@gmail.com> <56D5D2AD.6070805@gmail.com> <56D5DDA6.4080607@fleshgrinder.com>
 <40.73.36499.548B6D65@pb1.pair.com> <56D6BBD0.5010505@gmail.com>
 <56D73386.3000903@fleshgrinder.com> <86.68.21983.A2508D65@pb1.pair.com>
 <56D86C00.6000904@fleshgrinder.com> <12.FB.08749.AF759D65@pb1.pair.com>
 <56DAC26C.50304@fleshgrinder.com> <56DAE00F.2030203@lsces.co.uk>
 <56DAF480.7030508@fleshgrinder.com> <CAMPTd_B6VNQymDJo2MX03KrOWd1Mcfjg6gNY=GO1swxV8snrKQ@mail.gmail.com>
 <0B.E0.29316.019CBD65@pb1.pair.com> <56DBFDB5.1010806@fleshgrinder.com>
 <43.5B.29316.A864DD65@pb1.pair.com> <56DD64F5.5010503@gmail.com>
 <D7.70.03587.1B0AED65@pb1.pair.com> <56DEA829.5030903@gmail.com>
 <2D.96.15119.232FFD65@pb1.pair.com> <CAKnqCEZMh-P8XmAeQtdPnw4ZaZGb4=wmm_9QYZPhtuPUwaXLCA@mail.gmail.com>
 <76.21.53667.08C41E65@pb1.pair.com>
In-Reply-To: <76.21.53667.08C41E65@pb1.pair.com>
Date: Thu, 10 Mar 2016 10:53:11 +0000
Message-ID: <CAL0xaBFyR7oHdL6=7iCLBTc0jOMH6VHm+E5Zxr570mSPd_dDvg@mail.gmail.com>
To: Tony Marston <TonyMarston@hotmail.com>, internals@lists.php.net
Content-Type: multipart/alternative; boundary=001a11c32484a28f7f052daf9ff7
Subject: Re: [PHP-DEV] [RFC Proposal] var keyword deprecation/removal
From: arvids.godjuks@gmail.com (Arvids Godjuks)

--001a11c32484a28f7f052daf9ff7
Content-Type: text/plain; charset=UTF-8

On Thu, 10 Mar 2016, 12:29 Tony Marston, <TonyMarston@hotmail.com> wrote:

> "James Titcumb"  wrote in message
> news:CAKnqCEZMh-P8XmAeQtdPnw4ZaZGb4=wmm_9QYZPhtuPUwaXLCA@mail.gmail.com...
> >
> >>
> >> need to have their competence, professionalism, and intelligence
> >> questioned.
> >
> >Tony, making a statement like this is unprofessional in itself. You've
> >already been asked to put emotions aside and discuss this topic on the
> >technical merit,
>
> * rant content *


All that may be true for a language, that was designed in the first place.

PHP had a different path, one that made it grow organically and with lots
of mistakes, inconsistencies and other problems. All that means that any
effort to clean up the language and engine are going to break a lot of old
code whatever you do to the language. Heck, before PHP7 there where
limitations to the language parser that just prevented quite a few good and
sizeable rfc's from being implemented.

And as I said previously, var is actually missing functionality to be an
alias of public. They are not the same functionality wise. Var cannot
replace public in all cases.


I mean, I have 2 10-12 years old projects (no one actually knows how old
they are, just that it's 10+), that I do support. And that support includes
actually fixing a lot of problems, much more serious and impactfull than
"var". I'm running them on 5.6 in E_ALL mode, going to move to PHP 7 in
coming month or two.
You either maintain it, or you just get stuck on old PHP versions, that's
it. I did migrate them from 5.2 to 5.6 in one go - that was my first task
when I got them. And that doubled the performance too. The amount of stuff
that was dropped and changed in between these versions is huge, and still,
it was not hard at all. Mostly mondain stuff. So I perfectly do know the
hardships of legacy software in PHP - hype is overrated.

I have the opinion that the more hard the project is to support, the lazier
the developers that work on it are/were.

--001a11c32484a28f7f052daf9ff7--