Re[2]: [phplib] [RFC] Future of phplib From: Maxim Derkachev (max.derkachev <email protected>)
Date: 07/23/01

Hello Björn,

Saturday, July 21, 2001, 5:06:42 PM, you wrote:

BS> * Bertrand Mansion wrote:
>> positioning. PEAR : heavyweight, powerful but slower - PHPLIB : easier,
>> faster but not as complete.

BS> I think you've missed the sense of PEAR: PEAR is not
BS> "heavyweight, powerful but slower" (only if you refer
BS> to PEAR::DB, but I think you mean the whole PEAR),
BS> PEAR is and will be something like CPAN: a comprehensive
BS> repository of many classes like DB abstraction layers,
BS> auth classes, template classes and so forth.

BS> As PHPLIB is a framework with many classes (some depending
BS> on each other), it is predestinated that it (or some or
BS> most components of it) will be a part of PEAR.

The problem is that PEAR folks don't intend to build something like
CPAN (at least, this time). Many of them show themselves quite hostile
to the code coming from the outside. Sometimes they refuse to pass in
a code, because it was 'not invented here'. That seems to me that the
their goal today is to build a 'common' application framework, but not
the common classes warehouse, and anyone who wants to place some bits
there will face a strong opposition.
Me, personally, has survived a long conversation with Chuck about porting
PHPLib Session & Auth to PEAR. I'm not going to waste my time again.
I do think that your look at the pear folks and their views on reality is
quite a bit romantic. I bet you won't be allowed to place another db
abstraction layer there. At least, without a couple of pounds of your
blood. 

-- 
Best regards,
Maxim Derkachev mailto:max.derkachev <email protected>
System administrator & programmer,
Symbol-Plus Publishing Ltd.
phone: +7 (812) 324-53-53
www.books.ru, www.symbol.ru 

-- 
Abbestellen mit Mail an:   phplib-unsubscribe <email protected>
Kommandoliste mit Mail an: phplib-help <email protected>