On Tue, 22 Mar 2005, Perrin Harkins wrote: I have some anecdotal evidence of support. I told a couple of my co-workers about the PMC decision to change to Apache2. Their reactions ranged from "Thank god" to "It's the only sane choice." I was actually surprised that everyone was so in favor of changing the name.
I dont know if this will comfort stas is any way, but I am looking forward to this change and it has nothing to do with version numbers nor CPAN. When I see 'use Apache2', i dont see a version number. I completely concur with Stas that tieing it to a version number is a bad idea. But i dont care whether it is Apache2 or ApacheBlue or ApacheNextGen, so long as it is different from mp1 the namespace. I could care less if this fixes CPAN issues or not. I agree with stas (not to put words into your mouth... i think i am accurrately summarizing) that making a major API change to accommodate CPAN is a bad idea. But my user experience and happiness over the namespace change has nothing to do with cpan. I think there needs to be a major API change because the concept of considering mp2 to be mp1 with more stuff added, from actually using the two, is a flawed concept that was not fully appreciated until the path was trodden. No one is at fault... it just had to be explored in the real world before the correct path became 'clear' (ha). We have two different animals entirely here and they need to cut the cords that tie them together, such as namespace. mp1 and mp2 are sufficiently different (and incompatible) that, from my usage of them, they should be considered different products and hence have different names. I find it very misleading and confusing to think of mp2 as being version 2 of mod_perl. They are entirely different animals. So as a regular chump user and long time lurker, I think even if I agree 100pct with most of the points Stas raises (which i do), and discount CPAN and other motivations entirely, there STILL remains compelling reason to change the namespace. Basically I am advocating zero guarantee of compatibility between mp1 and mp2, and the simplicity that it will bring. As a long time reader, I read post after post trying to tapdance on eggshells to keep mp1 and mp2 playing nice together and the developer in me doesnt see a point to it. Rename them mod_perl_apple and mod_perl_orange and consider em both version 1.0 of unrelated products that happen to solve the same problems [not literally of course, just trying to illustrate my concept] - Perrin -- gedanken --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
