Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:73469
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.216.182 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <53352045.3020108@hoa-project.net>
References: <532FF7B9.5040700@hoa-project.net> <1395653827.9365.9.camel@guybrush>
 <532FFEDB.6010407@hoa-project.net> <slrnlj65b6.qd9.dsp@dsp.local>
 <5333CCD2.30604@hoa-project.net> <slrnlj8nhd.qd9.dsp@dsp.local> <53352045.3020108@hoa-project.net>
Date: Fri, 28 Mar 2014 12:34:23 +0200
Message-ID: <CAL0xaBH25aHYw1EPie3VGdzPO-T2Q+BspagR+bxaSDkfTY=3mQ@mail.gmail.com>
To: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a11c13da2fa391b04f5a83ff6
Subject: Re: [PHP-DEV] PHP Specification
From: arvids.godjuks@gmail.com (Arvids Godjuks)

--001a11c13da2fa391b04f5a83ff6
Content-Type: text/plain; charset=UTF-8

Hello everyone!

Took some time to read the discussion first before writing anything, so,
here are some thoughts from the userland developer :)

The idea of PHP Spec probably is floating around for a long time and for
good reasons. As we approach the time, when PHP.next becomes a reality, it
is a good time to do it.
I also think it is a good idea to revise if some rarely used PHP features,
that are not implemented in alternate implementations at all, are worth
keeping. Sure, this will not go unnoticed, but pros and cons. Some of it is
not implemented in alternate engines due to performance or is just not
worth it. So, an evaluation is in order I believe.

The second good thing that can come out of it is reevaluation of some type
juggling, clearing up some edge cases and probably finally dealing with the
type hints that generated so much heat and controversy on the list number
of times. On that note, clearing up and tightening up other edge cases is a
good thing.


BUT!

Before everyone gets on the wagon I want to remind everyone that although
PHP Spec is a good thing, there are other more important things to do for
PHP.next. The 64 bit support patch - there is a lot of work converting the
extensions ahead, and this is DAMN IMPORTANT STUFF. Way more important than
PHP Spec. The Unicode problem needs to be worked on too. The Zend Engine
iteration for crying out loud - it's last big update was like what, 10
years ago?
There are also interesting things happening - the Zephyr project, the PHPCC
lib for extension development - these are not just standalone alternate PHP
engines, these projects are directly tied with the original PHP, the one we
are talking about. Establishing a dialog and collaboration can benefit PHP
a lot (I dream of times when most of the PHP extensions could be written
with Zephyr without touching the low-level C - certainly would make
contributions much easier for many of us). Alternate PHP engines can
provide ideas and insights into updating the Zend Engine.

Just my 0.02$ as a userland developer, for whom the future of PHP is
important :)

Arvids.

--001a11c13da2fa391b04f5a83ff6--