I can't disagree with some of your sentiments, that new things are being
developed while there are some "old things" that are incomplete or in
dis-repair.
Unfortunately, PHP being developed as it is, there are only so many
people able to work on the core.
My own story with php-core was like this. I personally started using
accessors in other languages long ago and I was forced to use __get() in
php in order to have any sort of lazy loading or dynamic calculations.
My own large project has grown to the point where there are a few
__gets() that are just ridiculous in size and that's when I decided to
check out if PHP was ever going to get accessors so that I could
properly compartmentalize my code.
I found that Dennis had written an RFC several years before but never
had the time (or possibly the ability, not sure) to write it. I had
started with C and C++ some 20 years ago, but hadn't written in it in 8
or 9 years.
I had talked with Dennis about the original proposal and he helped me a
bit w/ the internals list/ideas/processes at the beginning, but really
it was up to me to get it done. So I stepped up and made it happen,
it's been a long road, the worst of which has been both the RFC process
(everyone has a voice, nobody has authority) and the lack of help for
the tough problems I encountered.
My point is there are only so many people that work on the core and if
they are not interested in improving it in the ways that you are, then
you need to step up and do it yourself. Learn C if you must, it has
some sharp edges but it's not an alien language.
It's nice to sit and point at all the problems, but if you can't fix
them yourself and you can't convince someone who can to do it, then
maybe it's time to step up and learn how to do it yourself, then
everyone can benefit; that's what I'm doing.
-Clint
On 1/11/2013 6:25 AM, Florin Razvan Patan wrote:
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.godj...@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!" © 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 stick
with it.
3rd problem is PDO. It lags behind for years and as far as I know from the
words of Perrie, no one is willing to touch it and it's a mess. I will not
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 these
problems should be addressed first before adding more stuff?
Arvids.
--
-Clint
