Re: [phplib] [RFC] Future of phplib From: Björn Schotte (bjoern <email protected>)
Date: 07/24/01

* Chris Johnson wrote:
> To me, that means moving PHPLIB to PEAR results in:
> 1) I have to rewrite large portions of my several applications which
> currently use PHPLIB.

Moving PHPLIB to PEAR is for "future" applications, i.e.
new applications that you write.

Imagine following situation: you're writing an application
that uses a class from PEAR. This class relys on PEAR:DB.
Then, you build Session/Auth around your application, i.e.
because it is a closed intranet. Session/Auth uses PHPLIB's
DB_Sql. So you have 2 DB abstraction layers in use.

Every code reviewer would say you're crazy because of
using 2 abstraction layers.

> 2) I end up with PEAR code that is slower and less efficient.

Prove it.

> 3) I have to wait another year or so before PEAR gets its act together
> and actually releases this stuff in a usable state.

Prove it.
 
> and as CPAN currently is) is a great idea. But the current
> implementation and politics of PEAR are detrimental, and the bottom line
> is not attractive.

Why don't you do something against that instead of
mourning and weeping around? 

-- 
PHP Schulungen und                        | International PHP Conference
Schulungsmaterial:                        |             05. - 07.11.2001
http://thinkphp.de/                       |      Astron Hotel, Frankfurt
http://rent-a-phpwizard.de/schulungen.php |  http://www.php-kongress.de/

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