Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:64860
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.219.43 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAL0xaBGm+=RF46ubMgOQqKkzu1sDykWiV_DZLUobYeZvyip-Pg@mail.gmail.com>
References: <50EFDEF7.4070408@lsces.co.uk> <50EFEB0B.2020103@cubiclesoft.com> <CAL0xaBGm+=RF46ubMgOQqKkzu1sDykWiV_DZLUobYeZvyip-Pg@mail.gmail.com>
Date: Fri, 11 Jan 2013 14:25:31 +0200
Message-ID: <CAA9esySjqER3xuEErtyX12uAkvqerGXSYcH1aw5ih-X__rBMPw@mail.gmail.com>
To: Arvids Godjuks <arvids.godjuks@gmail.com>
Cc: PHP Development <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] PHP is not ...
From: florinpatan@gmail.com (Florin Razvan Patan)

Hi Arvids,


This is exactly what I've stated yesterday here, you can read it
at http://news.php.net/php.internals/64820 but I've yet to receive
an answer for it.

The problem is that someone will actually need to implement the
whole thing again, in C, again, and it's going to be painful (again).

I can only say that I'm really sorry that I don't know C in order to
be able to contribute.

This is indeed a sensible subject and I wouldn't want to be hated
by the current developers / contributors but like I've said, at some
point it must be addressed.



Best regards,
Florin
----
Florin Patan / @dlsniper




On Fri, Jan 11, 2013 at 2:06 PM, Arvids Godjuks <arvids.godjuks@gmail.com>
wrote:
>
> I have to agree with Lester.
>
> It seems that there is a conspiracy to push annotations into PHP :D No,
> really, it's like goons decided that PHP needs annotations no matter what
> and just flooded the mailing list.
> I think: "The line must be drawn here, this far, no further!" =C2=A9 Star=
 Trek
> Before adding more major stuff we should cope with what was already added
> and get it into shape. Traits are getting a rewrite for the 5.5 release
> and
> APC can't catch up because of the traits. This is the first big problem
> that needs to be solved.
>
> Unicode is the second big problem. As far as I know there was some work
> done on mb_string like enabling func_overload by default, but there are
> functions missing that are in standard string extension. Just continue on
> course and get more people involved. Maybe make a roadmap and try to stic=
k
> with it.
>
> 3rd problem is PDO. It lags behind for years and as far as I know from th=
e
> words of Perrie, no one is willing to touch it and it's a mess. I will no=
t
> even start on the fact that it lacks tons of functionality and
> is extremely limiting when you start to do some serious stuff. The fact
> that virtually every framework bases it's DB layer on the PDO makes it
> even
> worse - a fast comparison between PDO and mysqli shows how limiting the
> PDO
> is.
> Just an example, mysqli has mysqli_ping. You can't do that in PDO, so I
> had
> to send a query "SELECT NOW()" every 10-15 seconds to the MySQL server to
> keep the connection alive. Because when PDO looses connection, it gives
> you
> an error and you can't just reconnect and continue.
>
> Oh, the PHP function API issue, like array vs string. Huge amount of
> improvements can be done here.
>
> This is just what gets into mind and I stumble upon regularly. Maybe thes=
e
> problems should be addressed first before adding more stuff?
>
> Arvids.