Re: [PEPr] Comment on RFC::Prefix all packages with P_

From: Date: Wed, 12 Jul 2006 18:29:52 +0000
Subject: Re: [PEPr] Comment on RFC::Prefix all packages with P_
References: 1 2 3 4 5  Groups: php.pear.dev 
Request: Send a blank email to pear-dev+get-43448@lists.php.net to get a copy of this message
Philippe Jausions wrote:
The fact that there is now a Zend Framework, is an hint to that PHP devs don't really care about PEAR. Furthermore given the ties between Zend and PHP, and that Zend Framework prefixes all classes with "Zend_" it will give leverage to php devs, to not include namespaces. Then it won't be long that Zend Framework will be bundled with PHP instead of PEAR. That would be a great waste of resources.
I know about of how internals works. I get all the rumours from the mouth when I attend various conferences. While your statements seem logical to an outsider, they make no sense for an insider. Internals does not follow what Zend says. Actually Zend has some PR issues if their own among most of the non Zend employed internals developers. So they have no chance in hell to get the Zend Framework bundled. Especially since some core developers work on "competing" projects like ez components. The fact that they are prefixing their classes was because they wanted to support PHP 5.x and it was obvious that no namespaces will make it into PHP 5 and more importantly not into PHP 5.0.x, the version Zend chose to support. So why did Zend start their framework project? There were no discussions at all with any PEAR developer as far as I know. Certainly nobody mentioned it to me and I would like to think that if they would have cared to cooperate with PEAR they would have approached me. I am sure if they would have approached the PEAR Group I would also know about it. But they dont. The exact reasons of why they started it are not clear to someone not employed by Zend. My guess it was another step for them in the direction of establishing themselves as the PHP company. They have no focus area. They provide proprietary products, developer on open source editors, open source PHP code, they do PHP consulting. So their strategy really seems to have a hand in anything that is remotely related to PHP. regards, Lukas

« previous php.pear.dev (#43448) next »