Re: Adoption of Metabase (was Re: [PEAR-DEV]Re:Comparing ADODB with PEAR DB, Metabase andNative MySQL)
| From: | Andr� N�ss | Date: | Tue, 20 Nov 2001 14:52:18 +0000 |
| Subject: | Re: Adoption of Metabase (was Re: [PEAR-DEV]Re:Comparing ADODB with PEAR DB, Metabase andNative MySQL) | ||
| References: | 1 2 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-3000@lists.php.net to get a copy of this message | ||
"Joao Prado Maia" <jpm@phpbrasil.com> wrote in message
news:Pine.GSO.4.40.0111200941340.5666-100000@mercury.alloy.net...
>> To me it seems like PEAR is too early in development for use in a
standard
>> production enviroment, and the documentation at pear.php.net is almost
>> empty?
>>
>Thats bullshit. We use PEAR::DB and several other PEAR packages at work
>and there is nothing wrong with that.
Well that's great.
> And you will fall to the same line:
>stop whining and write your own documentation then'.
:P
>I don't have the time to stop my work and write documentation, so I have
>to work with whatever I have now, which I think is good enough.
Fine. The point is that regular PHP users that go to pear.php.net to see
what PEAR has to offer will start wondering. If PEAR is going to become
widespread then there has to be documentation in place. When documentation
is missing I think: "Ah, so this package isn't really finished", and I don't
think I'm alone in that. Not all PHP users will have time to go through the
CVS and understand the entire PEAR structure, most will probably just be
interested in picking it up and start using it, with plenty of documentation
to help them do so. The FAQ clearly states that PEAR consist of software
that:
a.. has documentation about its API in the PHPDoc format
a.. has documentation/examples/tests (to be marked as stable)
André Næss