Re: GoogleAPI class

> >So how more packages there are in PEAR, the better. > > I respectfully disagree a bit here: Quantitiy is usually not equal > to Quality and I don't prefer quantity over quality. What i try to say is this: The company i work for is a gold microsoft partner. That means that i have always a hard time convincing people with in the company that PHP is just as good as ASP is. PEAR makes live easier for me. Especially the SOAP classes. As everybody knows webservices are very hot and promoted by microsoft. Almost everything is XML and SOAP. Now it's easy with PHP to communicate with SOAP webservices. The way for me is clear to convince my boss of the benefits and power of PHP. Another reason ASP is so populair (at my work) is the wide line of Active-X components that can be used. For commercial companies RAD development is very important. So the less classes I (we) have to write, the faster the application is ready and deployed. So in that context more packages in PEAR are better. Ofcourse is quality more important that quantity. Another pro for pear is the coding standard. Because everybody is using the same coding style it's 'easy' to change or adapt from a pear class. When i think a class could be useful to other developers, I commit it to pear. Ok, some classes are more useful that others. But the fact that those 'rare' packages are in pear makes it so unique and useful. And the main reason why PHP within the company i work for is rare is simply by the fact that ASP (VB) programmers are trying to write code in PHP in the way they do in VB. And that makes that the development time increases rapidly. Both now i've introduced the PEAR coding standards for the PHP developers development goes faster and faster. But enough talking for now. It's friday night, i'm free. It's party time!! So i leave you guys (and girls?!) alone, so don't delete the whole pear repository ;-) Dave Mertens