Re: The next biggest thing??? Maybe...

Alan, it's funny you compare Pear to CPAN. :) CPAN already has a number of applications and toolkits in it. 3 big ones spring to mind immediately! HTML::Mason, Apache::ASP, and Embperl. These three CPAN packages are NOT classes in ANY sense of the word. They are application toolkits/spring boards. They are "huge" (relatively speaking when compared to a class). So in that sense, PEAR SHOULD allow Binarycloud and PHPLib into itself. At least IMNSHO. -- Jeff Stuart jstuart@neo.rr.com "Alan T. Miller" <amiller@hollywood101.com> wrote in message news:KBEBLLJHLIHIEACOIFOCCEALCGAA.amiller@hollywood101.com... [...first part of message deleted...] > Someone mentioned that PEAR should follow in the footsteps on CPAN and used > that as a reason we should not consider doing something with PEAR. Yet, CPAN > was a system that grew out of a demand that existed in a PERL programming > environment years ago when the Internet then looked nothing like the > Internet now. I propose that we not simply set out to repeat the model of > CPAN when we are dealing with something that is much different. The world of > PHP development, is not the world of PERL development. The world of PHP > development exists because obviously something was missing in the world of > PERL development. I am not an expert but I would be willing to bet the very > number of PHP developers out there is beginning to rival that of PERL > developers, at least if it has not yet, in time it will. However, PEAR > should be more than CPAN... as for what that is, I cannot say for sure. All > I can do is maybe motivate some of you to think about PEAR in a different > manner, and see it's potential beyond what we all might have originally > envisioned, just as Rasmus did with his self made utilities to track his own > web site stats. [...rest of message deleted...]