Re: Whither PEAR2 (Was: Re: [PEAR-DEV] PEAR2 Standards)

Actually I'm sure there are lots of people who would love to see PEAR2 as it has been documented, however, the aims of PEAR2, are pretty incompatible with the current aims of PEAR1. In some seems to make more sense as a semi-seperate project. What I guess is really needed is a vision on how PEAR1 will continue while PEAR2 takes the focus of those that have been pushing it so much. Mixing what will become PEAR2 into the PEAR1 infrastructure looks like it will be confusing to users, developers and end users. Is it time to consider creating pear2.php.net ? - and cvs.php.net/pear2 (or svn..) for those projects and working out how to separate the two divergent projects? This will give considerably more flexibility for anyone working on a PEAR2 vision, to enable PEAR1 to thrive (or die...) in a reasonable manner... (On a slightly cooler head day ;) - Alan... Jeff Dickey wrote:

Alan and all, I, for one, can't wait for PEAR2. From what I've seen, lurking on the mailing lists, the team is at least trying to do a "proper" OO approach; granted, on a language that was not designed for it from the ground up and is showing increasing resistance to modern methods. PHP *has* been the "duct tape language" for quite some time pre-PHP 5; this really is the last great shot at crafting a system that can be used in core engineering-driven Web development, which has different requirements/styles/preferences than casual hacking. PEAR2, in my view, anyway, is imperative to: * effectively use and demonstrate current PHP language features; * promote more granular reuse than is practical with PEAR 1.x; * help maintain and expand the mindshare and usage of PHP 5 and later in wider ranges of environments; * whether we like it or not, be seen as "keeping up with" the competition (Python/Perl 6/Java/ASP.NET). Thank you all very much for your efforts!