Re: Horde components, deprecating old pear compontent

> > > As for advertising new APIs... Horde is not a direct "follow up" to PEAR, > is > it? That is a role for PEAR2 instead. Those components in particular are actually originally horde components, and they are filling the gap that a Log2, Text_Diff2, etc would. So I think in this limited case it's a better fit than PEAR2. > Given that, I don't think advertising > external packages will do any good to PEAR. Advertising PEAR2 equivalents, > sure, but not external ones. Otherwise, a good number of other packages > could also be dropped in favor of, let's say Zend. Thinking back to when zend framework was originally announced; I was incredibly annoyed that you had to get the whole framework just to get a single component. For a while; it wasn't pear installable; until unofficial sources sprung up. The thing that has changed since is that pear channels are dead easy now - and Zend, Symphony, etc are moving towards individual components being installable. We've also got diminishing contributors and a lot of old code - people are tackling some of the problems we are in other frameworks or locations. Why not embrace our strengths - pear channels - and let other people in other areas re-solve problems for newer versions of PHP. That way we can focus on unique or boutique packages that solve a niche need of ours, without a whole lot of "not invented here" effort. As you say; you find Zend_Mail's API to be cleaner than Horde or PEAR's offerings. If it's actually the best of breed, developers are going to choose it - so why not help that package out?