Re: [binarycloud-dev] Re: [PEAR-DEV] Re: [metabase-dev] RE: [PEAR-DEV] New Metabase Aniversary release

* Alex Black wrote: > > Of course, but no one forces you to do that. I, as a developer, > > can choose if I want to use PEAR::Metabase in my application > > or PEAR::DB. > Yes, which is not a good idea. If you're tying to get people to use a common > set of high quality classes, you'll need to introduce some standards. But furthermore you need to assure that you don't influence people too much while promoting PEAR as the new solution on PHP's heaven. > difference. I have no interest in PEAR as an application framework, I like > it as it is: pool of classes that follow coding standards. Yep. > If PEAR will allow multiple versions of a foundation component like database > abstraction, then PEAR certainly is CPAN, with coding standards added. I really don't think so. If it would be, I can't see any disadvantages. Why should PEAR people force the developers to use "the one and only" DB abstraction class? > CPAN is huge and tangled because its owners did not want to make decisions. PEAR should not be a monopoly where PEAR activists decide what should be and what not. > Just decide: is PEAR: > -CPAN with coding standards > -PHP Base Classes Life is more than black and white. -- PHP-Schulungen in Frankfurt und München! Mehr Informationen? >>> mailto:bjoern@thinkphp.de