Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:71723
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain kingsquare.nl from 141.138.142.202 cause and error)
MIME-Version: 1.0
In-Reply-To: <52E8C097.6080208@lsces.co.uk>
References: <CAEZPtU6749gD2a9BDzdTQoBPUsPDSspjukZvFw9qwt=Le5Q1zQ@mail.gmail.com>
 <CAGa2bXbfO-x9kMkC6UWujJbzVZrRdQ_N=PsZchGtXjGnxXRFKg@mail.gmail.com> <52E8C097.6080208@lsces.co.uk>
Date: Wed, 29 Jan 2014 12:22:50 +0100
Message-ID: <CADq_CxrS1xmcZN7Bstg3uXnQAtj3-sOo+qVX64V_ZEaZOZqDnw@mail.gmail.com>
To: PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] some thoughts about php 6
From: robin@kingsquare.nl ("Kingsquare.nl - Robin Speekenbrink")

Just chiming in from the user point of view:
after being a PHP developer since PHP4 and using OO principles since
PHP4 (yes, it happened) and now living the dream with 5.3+ I
personally see absolutely no reason to change the function names etc.
Or even the camelcasing issues that might be there... As a user i'd
just like to see something that someone already mentioned: PHP growing
as a language to support the modern way of HTTP: sockets,
non-blocking, etc etc. Performance is everything. What i type (and how
i type it) is my business. If that's needle/haystack or
haystack/needle, doesnt matter in my book. As long as my IDE / muscle
memory kicks in when needed i'll be just fine.

Now for PHP to actually move towars a faster engine / JIT /
whathaveyou th=C3=A1t would be something i'd love to see. Also being able
to move my codebase to newer major releases with 'varying' ease is a
PLUS! The whole python2/3 issue should be avoided when possible.
(imho)

I really like the upgrade path starting from 5.3: minor breakage and
where it _might_ break it would be for the better anyway...
(performance / security POV)

As to give my personal list of priorities for the language as a whole:
- really make the new(er) features shine vs the old and gray
  array_walk / callbacks are still a fraction slower than 'simple',
but less elegant, foreach structures....
- improve the 32/64 bit differences
  as already being discussed in a seperate RFC
- better tooling for finding bottle necks right out of the box
  I'd like a built in syntax / compiler / hhvm style checker to
analyze my project ... Without having to resort to external seperately
built tooling. Allowing some kind of compiler to actually tell me
where i could improve / cleanup my codebase would help me a lot.


If people are really adamant in creating OO versions of string / array
functions: nothing stops them from doing that in userspace today. (the
same goes for the aliasing of functions)

ok. that's me done ranting ... Just a small fish in a large ocean of
PHP sharks :)

In any case; good luck shepherding the development of such an
important and widely used language!

Regards,
Robin Speekenbrink