Re[2]: [PEAR-DEV] Some more plane hacking...
| From: | Nicolas Hoizey | Date: | Thu, 16 Aug 2001 11:43:35 +0000 |
| Subject: | Re[2]: [PEAR-DEV] Some more plane hacking... | ||
| References: | 1 2 3 4 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-1564@lists.php.net to get a copy of this message | ||
> Please don't cut the other reasons :-)
I just wanted to comment one of them, so I found logical to keep only
this one ... The others are in the archives. :)
>> Speed is often a real issue for professional use of PHP, so having
>> some of the core components of PEAR available as extensions would be
>> great !
> Let's define "professional". I have one server with 1,5 millon
> _hits_ a day with php, templates, postgres, and it's running fast
> and smooth.
Great, but what is the mean time of each request ?
Do you use any caching tool ?
I think Zend Cache would increase a lot PEAR based developments
performances, but I have never tested it. "Professional" leads to
"profit", and I think those who have money should use Zend Cache.
> The amount of speed you can gain optimizing classes is nothing
> compared to optimizing queries, databse, SO, web server.
I agree, but IMHO, having database abstraction and error handling in
the core of PHP would be a really good thing. Not only for
performances, but also for ease of use.
>> I think it could be possible to have both the C and the PHP versions
>> running together, the right choice being made "automagicaly", don't
>> you think ? :)
>
> If so, yeah no problem and no more discuss :-).
Great.
> But I (and I'm sure many others) don't want to spend > 4 hours
> propagating changes of a C extension thru servers with differents
> operating systems/c libs, when I can do it in two minutes with
> .php's.
I also prefer php over C (maybe because I fear compilation stage) but
we are talking about stable classes which are rewriten in C, so their
API should not change, and there is no compatibility issue here ...
> Just ask a question if you let me: the guys who are promoting C
> extension will join to pear and work in the this C extensions? will
> maintain them? will ensure cross-platform/cross-compiler ability?
> will attend bug reports?
As for other extensions, the maintainers are responsible of all that,
and each extension/class/package has it's own "vitality" which tells
us if it's reliable.
I apologize if my speach is not clear, but it is a simple mirror of
my boiling brain ... :)
-Nicolas
--
Nicolas "Brush" HOIZEY
Free PHP projects http://www.phpheaven.net
Veille tous azimuts http://www.gasteroprod.com